Logout Users on database that needs to be repaired

[DT]

Once in awhile we run into a problem where a database needs to be repaired. The problem is that there are users still in the database. I set up a table and logout form but you can't open the database to use it. Is it possible to kick them out of the database?

DT

 

[llkhoutx]

I've done it by using a hidden form in the FE which uses the timer event to check a table. Depending on a value in the table, the user is given a popup message to log off, then after another interval if that user is still "on", the hidden form causes the user's application to "quit." User's don't like it, but they're warned. Sometimes they've just walked away and left the application running.

 

[mark curtis]

If the database is on a server then just get admin permissions on that server and boot them off it. remove the db for repair!!

 

[DT]

Mark,

I talked to our Database/Network Administrator about this before I posted. He said this wasn't possible or didn't know how or what to look for to do this. Could you explain a little more..."get admin permisstions on that server and boot them off of it" I need a little more info so I could explain it to him or his boss.

Thanks for the help,

DT

 

[mark curtis]

how is the db set up? client server? server?

what sort of Server is the db on?

eg if it is NT he just gives u admin rights on the server and u use servmgr.exe to boot them off!

 

[DT]

Mark,

We are running on a Novell Server and the database is installed on a network drive. Nothing, except access, is local.

When you say admin rights on the server, are you saying all rights to the folder where the database resides? If so, I have these rights. Where might one look for servmgr.exe?

Derek

 

[The_Doc_Man]

The way I would approach this would be to use a startup form. (I have one, but it doesn't do the kick-out.) It does some logging for me so I can track usage. My users have to click a button on the form to get past it.

When they click the button, the form doesn't go away, it just minimizes and goes non-visible. But it has a timer in it. Once every so often, the timer wakes up to check the current time of day and the first record in my "DB Events" table. This table has a descriptive field and some time fields. If the current time is between the start and end time for an event, the user gets a message box warning of the event. Right now I am on the honor system, which works in my shop. But they know I could do much worse things to them if I needed to.

I suppose you could adapt this code to include an option to kick folks out. I would do it by checking the user ID or group ID. If they are not supposed to be there, I would open an OKOnly box, letting them click "OK" on the box that says "You are about to be kicked out." Then immediately do a DoCmd.Quit on them.

 

[llkhoutx]

The solution I proposed works.

 

[DT]

Thanks for the help...I did get something to work. I have a hidden form with a timer that when refreshes looks for the LOGOUT.TXT file located on our network. If it does locate the file, the database closes. If not...the database does nothing. So, if the database is corrupt and needs to be repaired...I create the LOGOUT.TXT file and shuts the database down. I do have to remember to delete the file though, otherwise the database keeps closing.

DT