How do you knock out users or Disconnect users from a database remotely?

[anoble1]

I have multiple Access 2003 databases. I do most of the editing in them all the time. I am having a problem of users all over the state being in the database, and won't get off of it. I currently use LDB Viewer. (Which just tells me the computer name that's currently connected). But, is there a way I can write something that will knock everyone out, of whomever I choose, so I can edit the database?

Thanks

[Megalog]

Twinny,
Sadly, I dont have an easy copy/paste code solution to provide for this. I posted my basic approach at the beginning of this thread, and you should use this as a roadmap to your custom approach. It will involve the use of a hidden form with a timer, a small table to store the login/logout information, and basic code to save & close access.
If you get stuck on any specific steps, leave a detailed post and I'll try to provide an answer.

[GrnMtn7]

@anoble1
I found a simple solution a year back or so that involves opening a form Let's call it zzMXLOCK with the autoexec macro. It opens hidden and the OnLoad Event looks like this:

Private Sub Form_Load()
Dim strFileName As String
strFileName = Dir("X:\NetworkFolder\Subfolder\LOCK.ozx")
        If strFileName <> "LOCK.ozx" Then
        Application.Quit acQuitSaveAll
        Else: DoCmd.OpenForm "zzMxShutdown", acNormal, "", "", acFormReadOnly, acHidden
        DoCmd.CLOSE acForm, "zzMxLock"
        DoCmd.OpenForm "MAINNAVIGATION PAGE”
 

This will only work for a split database where you can have the form “look” for a specific file
By renaming the file when the database goes to load and the macros are enabled (use .accde Or .mde)
The one form loads sees the file doesn’t exist and keeps the user from entering the DB. This locks the database, now the form “zzMXShutdown”m entioned above does that same thing but on Open and On Timer. To be nice I add a form called “zzAppShutdownW arn” that lets the user know they are about to be booted. The nice thing about calling a form and not a message box is you can more easily tailor the message later.

Private Sub Form_Open(Cancel As Integer)
    ' Set Count Down variable to false
    ' on the initial opening of the form.
    boolCountDown = False
End Sub
 
Private Sub Form_Timer()
On Error GoTo Err_Form_Timer
    Dim strFileName As String
    strFileName = Dir("X:\Networkfolder\Subfolder\LOCK.ozx")
    If boolCountDown = False Then
        ' Do nothing unless the check file is missing.
        If strFileName <> "LOCK.ozx" Then
            ' The check file is not found so
            ' set the count down variable to true and
            ' number of minutes until this session
            ' of Access will be shut down.
            boolCountDown = True
            intCountDownMinutes = 2
        End If
    Else
        ' Count down variable is true so warn
        ' the user that the application will be shut down
        ' in X number of minutes.  The number of minutes
        ' will be 1 less than the initial value of the
        ' intCountDownMinutes variable because the form timer
        ' event is set to fire every 60 seconds
        intCountDownMinutes = intCountDownMinutes - 1
        DoCmd.OpenForm "zzAppShutDownWarn"
        Forms!zzAppShutDownWarn!txtWarning = "This application will be shut down in approximately " & intCountDownMinutes & " minute(s).  Please save all work. There will be no other warning"
        If intCountDownMinutes < 1 Then
            ' Shut down Access if the countdown is zero,
            ' saving all work by default.
            Application.Quit acQuitSaveAll
        End If
    End If
 
Exit_Form_Timer:
    Exit Sub
 
Err_Form_Timer:
    Resume Next
End Sub

[kdcrowley]

I also use a hidden form to track login info, which also stores a yes/no checkbox, which I can uncheck at anytime. Every 60 sec, the form checks for "loggedIn", and if 0 then opens a warning page. The warning page gives the user 45 sec notice to get out, and then does a DoCmd.Quit acQuitSaveAll. I've considered running code to change (temporarily, of course) that user's login info, so they can't just jump back in, but haven't needed it yet.

[ahd2008]

That's interesting discussion. Megalog, I am concerned to know what code you use to perform the kick off safely and save the records that are being used when you said " then it saves whatever record they are working, logs them out, and closes access"

Thanks

[Megalog]

After all the checks and measures are done, and the user logging is complete, I believe all it does is:

DoCmd.RunCommand acCmdSave
DoCmd.Quit