You'll need to disable pooling. I think you can do that by using their DriverManagerDataSource implementation (IIRC).
Cheers,
Clinton
On 7/30/06, Gwyn Evans <[EMAIL PROTECTED]> wrote:
Well, I'd still try & take a look to see if there's anything you can
do to ensure that all connections are closed, as there's no suggestion
that the bridge is not working for you in any other way.
/Gwyn
On 29/07/06, AlexeyG <[EMAIL PROTECTED]> wrote:
>
> Thanks for your responses!
>
> MS Access is used only for data import... admin uploads the MS Access DB
> and I import records. Successfully imported records get deleted, failed
> records remain. Admin can then download the DB back and fix failed records.
>
> I need that lock released so that I can "compact" the Access DB by launching
> "access.exe *db path* /compact... Without compacting the Access DB remains
> the same size even if all but few records are deleted... It is a bit of a
> pain, but I'm pretty much stuck with that process.. At least I do not have
> to deal with tables to store failed import data, or write an interface to
> allow admin to fix it.
>
> Sounds like getting a good driver or using JDBC straight up and releasing
> connections is the way to go... Thanks!
> --
> View this message in context: http://www.nabble.com/MS-Access-LDB-locks-using-JDBC-ODBC-bridge-and-iBATIS-tf2017245.html#a5558867
> Sent from the iBATIS - User - Java forum at Nabble.com.
>
>
