Booting user off network database from a different machine

[AccessNut]

Hi, I have a recurrent issue with users parking in a network access database. I need to get them out of the database for doing things such as changing the design of a form. Sometimes they get into the database and forget to exit and if they are not in the office I cannot go just shut their computer off. Is there a way for me to kick them out by doing something from my machine? I know you can track idle time but I don't want to do that. I also tried splitting the db into front end and back end and that did not work well either.

I need some way to kick them out on an as needed basis, if that is possible. I know their usernames. Thanks in advance.

 

[DavidAtWork]

The database should be split, frontend-backend, and then there's no issue about kicking them out. You just make changes to your frontend and issue an update.
Why didn't splitting the database work for you. If you're worried about updating user's version after you've made changes, there are several ways to control this
David

 

[AccessNut]

I did split it and tried it out. It was too slow for my users. We have about 20 people using it and if more than 3 are in it at the same time it almost grinds to a halt. Sadly new machines is not an option :-(

It is only an issue if someone is not in the office but left their machine on and did not exit the database. I was hoping there may be an easy way just to kick them out by doing something from my machine.

 

[DavidAtWork]

wow, sounds painfully slow, have you contemplated a sqlServer backend. I work in a place where we have 40 users with this kind of setup and no performance issues at all, although as you've hinted, it may be down to individual machines.
David

 

[Alansidman]

Look at this:
I found it a couple of weeks ago but did not implement as we are using an RDC and found a way to kill the user in the processes of the remote server.

http://www.databasejournal.com/feat...8586/Auto-Logout-Users-for-DB-Maintenance.htm

Alan