I have to agree with Brandon - the JDBC-ODBC driver is total rubbish.
It's only value is to provide you with a way to get your data out of
M$ Access and into a real database.

Trying to do more with it is insane.

Larry

On 7/28/06, Brandon Goodin <[EMAIL PROTECTED]> wrote:
Don't use JDBC-ODBC bridge... it's horrible and useless. There are no Open
Source Access JDBC Drivers. You will need to purchase one. I would recommend
that you look into using a real database. Something like MySQL or PostreSQL
if you are looking for affordable.

Brandon Goodin


On 7/28/06, Carson Reinke <[EMAIL PROTECTED]> wrote:
> Did you try to close all the connections?  It is a bit complicated with
> Spring, but I believe if you have every bean to set to
> "singleton=false", the connection might get reset.
>
> Thanks.
>
> Carson Reinke
> [EMAIL PROTECTED]
> P: 248.333.7700 x108
>
> -----Original Message-----
> From: AlexeyG [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 28, 2006 3:47 PM
> To: [email protected]
> Subject: MS Access LDB locks using JDBC-ODBC bridge and iBATIS
>
>
>
> Hello,
>
> I am attempting to use iBATIS and to access MS Access file via JDBC-ODBC
> bridge.
>
> (I am using Spring's "SqlMapClientDaoSupport," but that is probably
> irrelevant)
>
> All this runs on Tomcat...  First time DB gets accessed the LDB lock
> file is created.  From there on the only way I can remove the lock file
> is to kill the JVM...
>
> Any help is greatly appreciated...
>
> - general ideas/info on the way iBATIS behaves with JDBC-ODBC bridge and
> locks
>
> - maybe I can somehow get Spring to reset the bean?
>
> --
> View this message in context:
>
http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBA
> TIS-tf2017245.html#a5546027
> Sent from the iBATIS - User - Java forum at Nabble.com.
>
>


Reply via email to