Experts:
Much has been published on the topic "Kick user(s) out of an Access database/backend". In fact, there appears to be an overwhelming amount of recommendations how to "gently" do so w/o a) causing potential data errors and b) ending up with a number of frustrated users.
At this time, I have come across a simple, but effective, example database (published in 2005 @ https://www.databasejournal.com/feat...aintenance.htm#). I like the simplicity of the demo version and it appears it works just fine as long as I am in the same frontend.
Here' how I tested the demo DB:
a. I split the database into "backend" (BE) and "frontend" (FE) and linked the BE table to the frontend.
b. For mimicking multi-user login, I created two shortcuts to the FE. I called the 1st shortcut = "User 1"; 2nd shortcut = "Admin".
c. Then, for testing purposes, I had a user login as "User 1" while I selected shortcut "Admin".
d. As the Admin, I then executed the Logout form.
e. For me (admin), the 3-minute countdown started almost immediately. For User #1, however, there was a slight delay but ultimately the "warning message" appeared and eventually both databases were shut down after 3 minutes.
THIS WORKED GREAT!!
BREAK BREAK...
Now, here is where (I believe) I need some assistance given that my process of using the FE is different. Please allow me to recap the differences:
1. As mentioned in b) and c), I created two shortcuts (User #1 & Admin) -- both of them were linked to the same FE on the network though.
2. In my case, however, I do NOT share the same FE on the network. Instead, our users have their individual copies of the FE on their client machines. Now, in the event I make a change to the MASTER FE on the network, the client FE will automatically download a copy of the MASTER FE which will then replace the FE on the client machines. The AutoUpdater process works great (see details @ http://www.utteraccess.com/forum/Eas...r-t304808.html) and I do NOT want to change how users automatically get the latest version of the MASTER FE. But they, the "AutoUpdater" topic is another topic... I digress.
Back to the AutoShutdown (demo version). I believe this AutoShutdown process worked given that both User #1 & Admin ultimately used the same FE (on network), right? Alternatively, in my process, I'm not 100% certain if the "shutdown warning message" would appear on User #1's FE given we have individual FE copies on our C-drive. So, I don't see how my initiating the "shutdown" process would generate the warning pop-up on another person's client FE.
My question: Am I missing something obvious? If my assumption, however, is correct and the recommended auto shutdown won't work in my situation, is there another way I could tweak the example file? If so, how?
Lastly, if the latter is not feasible, does anyone have a recommendation for another solution that supports the shutdown of individual FEs on various client machines?
Thank you,
EEH