Close Access application remotely ODBC issue

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using the procedure at http://support.microsoft.com/kb/304408/en-us to
shut down access remotely so I can do maintenance on the database. The
procedure is working fine but I believe I’m having issues with my ODBC
connection. After Access closes I'm still not able to open Access
exclusively. I check all users’ computers and the application is not open
but I still get the message. I have 1 procedure in my db that sucks data out
of an ODBC table to refresh the data in an access table. If that procedure
has not yet occurred then the Application.Quit works fine and I can open the
db exclusively. If it has occurred then I am unable to get in exclusively.
I have to physically reboot all the users’ computers to get back in. What’s
being left open and How? Is there away I can make sure the ODBC is
disconnected before I close the application?
 
I am using the procedure at http://support.microsoft.com/kb/304408/en-usto
shut down access remotely so I can do maintenance on the database. The
procedure is working fine but I believe I’m having issues with my ODBC
connection. After Access closes I'm still not able to open Access
exclusively. I check all users’ computers and the application is not open
but I still get the message. I have 1 procedure in my db that sucks data out
of an ODBC table to refresh the data in an access table. If that procedure
has not yet occurred then the Application.Quit works fine and I can openthe
db exclusively. If it has occurred then I am unable to get in exclusively.
I have to physically reboot all the users’ computers to get back in. What’s
being left open and How? Is there away I can make sure the ODBC is
disconnected before I close the application?
Click to expand...

I will guess that in that procedure you mention, you might have
forgotten to close a connection or set one or more object variables to
Nothing before exiting the procedure.

Have you tried creating an ODBC trace log? You can turn on tracing by
going into the Control Panel / Administrative Tools / ODBC Data Source
Administration and clicking on the "Tracing" tab.

You should be aware, however, that tracing will slow things down to a
crawl, and the log files can get VERY large. Be sure to turn it off
when you are done, too!

I have also noticed on more than one occasion that turning tracing on
or off doesn't always "take" the first time around, so when you turn
it off, do some tests to make sure that it hasn't come back on again
by itself. The trace function documents every single ODBC API call
made by every connection using any ODBC data source you have installed
on the client. This is why it is a performance killer and writes huge
files. You should be able to find out eventually what is happening and
why.

HTH,
 
Back
Top