S
Steve
It appears that Access keeps ODBC connections open for
about 10 minutes after it is last used. I need to copy a
file after Access manipulates the data via ODBC.
Attempting to copy the file immediately after Access
finishes fails with a file in use error. Right now I can
either wait 10 minutes or close Access. If I close Access
I can copy it immediately.
Is there any way to get Access to release an ODBC
connection sooner? Any setting or registry entry?
Is there any way using VBA?
Thanks
Details:
Access 2002 sp2
Windows XP sp1
Sybase Adaptive Server Anywhere 6.0
(although I have seen this behavior with other versions of
Access and other ODBC drivers)
For performance, I have to copy the Sybase DB to a RAM
drive, do massive updates, then copy back to a real drive.
I have code that does all these steps, including the user
browsing for the file etc. Only problem is waiting 10
minutes.
<sigh>
about 10 minutes after it is last used. I need to copy a
file after Access manipulates the data via ODBC.
Attempting to copy the file immediately after Access
finishes fails with a file in use error. Right now I can
either wait 10 minutes or close Access. If I close Access
I can copy it immediately.
Is there any way to get Access to release an ODBC
connection sooner? Any setting or registry entry?
Is there any way using VBA?
Thanks
Details:
Access 2002 sp2
Windows XP sp1
Sybase Adaptive Server Anywhere 6.0
(although I have seen this behavior with other versions of
Access and other ODBC drivers)
For performance, I have to copy the Sybase DB to a RAM
drive, do massive updates, then copy back to a real drive.
I have code that does all these steps, including the user
browsing for the file etc. Only problem is waiting 10
minutes.
<sigh>