Close all connections

[esskaykay]

I have a few DB’s that run an “update” query nightly. However, if someone forgets to close their connection, the update fails to run. I’m looking for a procedure or other routine that automatically closes all connections to a database.

I’ve tried a couple I found (KickEmOut, LogOff2K) but these only close the front end of a FE/BE system. My primary concern is with a third party app (ArcView). This is a geographical Information System (GIS) that links graphical mapping to database attribute data. If someone forgets to close ArcView, the connection to my DB remains open – thus no update. What I’d really like is some way to close all connections when the BE opens.

Any suggestions would be greatly appreciated.

Thanks,
SKK

 

[The_Doc_Man]

Usually, closing the FE of a FE/BE pair closes the BE too. Unless there is a DAO type of connection that doesn't go through the FE. The problem is that you need to see something that normally isn't available to Joe Average User. A "netstat" command might show you all open connections to the computer and you might then be able to do something about the ones from user workstations. But sadly, unless your users close what they open, you are going to always be stuck.

At least for the FE, I always used a startup form that didn't go away. It just hid itself and minimized itself, but it was always there. If you then walked away from it, it was still there watching you. It had access to a table where I could write a date/time for the next expected down time. If you crossed that date/time, it issued a DoCmd.Quit for you and shut down your FE.

I've not heard of the BE staying open, though, unless you have some non-Access app (say, something in VB6 or Java) through ADO or DAO. The key would be to have those apps also check for whatever condition you want to use for a signal and also do an exit or quit or whatever at the appropriate time.

 

[ezfriend]

May not be the best solution, but it's a suggestion.

I did something similar in that nature in the past. Since I didn't have much control over third part software, what I ended up doing is create a small application that would shut down any application specified in a text file.

This small application open a text file from a network folder. let's say v:\checkapps\shutdown.txt.
The application will read every minute to see what's in the shutdown.txt file.
If it contains an application name (word.exe) then loop through the processes running and shut it down. If it contains "NOTHING" then just keep running in the background.

That did the trick for me.

EZfriend.

 

[esskaykay]

That may be a bit beyond my capabilities. Could you forward an example so I could play with it a bit?

Thanks,
SKK