"kicking" users from a database

[seansan]

Another Q,

Because we sometimes need to repair the shared database I would like
to find out if there is a way to "kick" all users from a database. The
problem is that I cannot repair the database when it is beeing
accessed by another user and this almost always seems to be the case.
With another tool I downloaded I can identify the users still in the
database and send them a NET message to exit the DB.

Does anyone know how I can do this programmaticall y, or if I can deny
users access to the database for a while?

thx, Seansan

[Bas Cost Budde]

seansan wrote:

Another Q,

Because we sometimes need to repair the shared database I would like
to find out if there is a way to "kick" all users from a database. The
problem is that I cannot repair the database when it is beeing
accessed by another user and this almost always seems to be the case.
With another tool I downloaded I can identify the users still in the
database and send them a NET message to exit the DB.

Does anyone know how I can do this programmaticall y, or if I can deny
users access to the database for a while?

Common approach to this is to have a form open, but hidden; the form has
a Timer event, and checks on every timer for a certain condition (some
file on the network exists, or some record exists in some table--you can
use that if tables sit in a backend on a shared location). If the
condition applies, display a message and issue a Quit statement.
--
Bas Cost Budde, Holland
http://www.heuveltop.nl/BasCB/msac_index.html
I prefer human mail above automated so in my address
replace the queue with a tea

[Forrest]

> Does anyone know how I can do this programmaticall y, or if I can deny

users access to the database for a while?

There's no built-in way to do this, so you have to code your own
method. Basically, what you would want to do is:

Create a table that's going to let you know whether access is allowed.
Call it USys-something, because the database will hide it, even if
you check 'show hidden objects.' It won't confuse anyone, and nobody
will know to tamper with it. You could either just have one row with
a yes/no field, or a history and scheduler.

Then on each form and report, have a function that checks your table,
and closes the database if you've put it off limits. Call your
function when the form loads, and probably on a timer.

[Hank Reed]

I have been doing that for a couple of years on a system in our
factory. I have the main menu check once per minute for an entry in a
table that says that I need the database. When each user's code
detects the flag, a routine closes all the forms except the main menu
and a dialog box is displayed explaining the situation. The main menu
does not access any tables so I am free to do whatever maintenance is
required.
I prefer this method as opposed to shutting down their
application because then the user would not know exactly what has
happened. The dialog box stays up, the flag is checked again, once
per minute, and when the condition changes, the dialog box is closed
and the user can continue at will.
I use the following code to close all forms. There are probably
better ways but this works.

Dim obj As AccessObject, dbs As Object
Set dbs = Application.Cur rentProject
' Look for open forms
For Each obj In dbs.AllForms
If (obj.IsLoaded) Then
strName = obj.Name
' Close all open forms except "Main Menu" and "QuitForm"
If ((strName <> "Main Menu") And (strName <> "QuitForm") ) Then
DoCmd.Close acForm, strName, acSaveYes
End If
End If
Next obj

[Trevor Best]

Hank Reed wrote:

I have been doing that for a couple of years on a system in our
factory. I have the main menu check once per minute for an entry in a
table that says that I need the database. When each user's code
detects the flag, a routine closes all the forms except the main menu
and a dialog box is displayed explaining the situation. The main menu
does not access any tables so I am free to do whatever maintenance is
required.
I prefer this method as opposed to shutting down their
application because then the user would not know exactly what has
happened. The dialog box stays up, the flag is checked again, once
per minute, and when the condition changes, the dialog box is closed
and the user can continue at will.
I use the following code to close all forms. There are probably
better ways but this works.

Dim obj As AccessObject, dbs As Object
Set dbs = Application.Cur rentProject
' Look for open forms
For Each obj In dbs.AllForms
If (obj.IsLoaded) Then
strName = obj.Name
' Close all open forms except "Main Menu" and "QuitForm"
If ((strName <> "Main Menu") And (strName <> "QuitForm") ) Then
DoCmd.Close acForm, strName, acSaveYes
End If
End If
Next obj

You're too kind to your users, I give users plenty of warning by use of
the polled table mentioned elsewhere in this thread, then if they're
still in then tough titty, they should know better than to defy me :-)

Actually it's defying the client's admin bod, but I give him the means
to do it and the "Kick Users" button has been renamed "Kill Users" by
request from one of them, something I gladly complied with, didn't even
charge him for that one.

--
This sig left intentionally blank