> One thing you might want to know is that MS ACCESS database is not
good
> for concurrent write access (it's a well-know defiency) -- the
database
> will be corrupted if this occurs and all your data is lost. If you're
> just extracting data you should be ok.
Access is no enterprise database, but this is FUD. MS Access handles
concurrent write access quite well with a page-based locking and
optimistic locking mechanism. It works as well as well as any other
non-client-server database. It is not a defiency of Access that can
cause corruption, it is network or client software failure partway
through a database write that causes corruption - just like any other
file-server (non C/S) database.
Back in the Access 2.0 era, I had an application with 25 users accessing
(read/write) heavily the same MDB all day - the only time corruption
occured was when the file server, network, or client software died
mid-update.
Of course, the answer is still the same... Value your data? Put it in a
real client/server database!
[ Kyle Cordes * [EMAIL PROTECTED] * www.kylecordes.com ]
[ Training and Development Services: Java, Delphi, PHP, ]
[ ASP, ASTA, Web Applications, n-tier systems, etc. ]
[ Delphi developers: Visit the BDE Alternatives Guide ]
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
