i agree, access is a very poor choice of db for ANY production system. matt ----- Original Message ----- From: "Craig R. McClanahan" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Saturday, April 06, 2002 8:08 PM Subject: Re: Is there a native JDBC driver for MS Access?
> > > On Mon, 8 Apr 2002, Adrian Beech wrote: > > > Date: Mon, 8 Apr 2002 10:38:45 +1000 > > From: Adrian Beech <[EMAIL PROTECTED]> > > Reply-To: Tomcat Users List <[EMAIL PROTECTED]> > > To: Tomcat Users List <[EMAIL PROTECTED]> > > Subject: Re: Is there a native JDBC driver for MS Access? > > > > Ummmmm, okay then how stable is the JDBC/ODBC bridge? As I previously > > mentioned in my initial posting some bits and peices that I've read suggest > > that this method of connecting to a DB back end is, or can be, a little > > dodgy. The comments basically revolved around the premise that the bridge > > is not capable of being threaded and it is considered by Sun to still be > > experimental. I got the impression that there is potential for data loss or > > corruption along with performance related issues. > > > > The JDBC/ODBC bridge is not appropriate for use in a multithreaded > environment like a servlet container. Also, lots of people have had > problems trying to use MS Access (designed for personal desktop use) in > environments like this, even with a for-pay JDBC driver. > > I'd start by choosing a different database. > > > I guess I really need to know if it is reasonable to use Tomcat to host an > > environment that relies on this sort of DB connectivity. > > > > Adrian > > [EMAIL PROTECTED] > > > > Craig > > > -- > To unsubscribe: <mailto:[EMAIL PROTECTED]> > For additional commands: <mailto:[EMAIL PROTECTED]> > Troubles with the list: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
