How can I kick out multiple users of the same Access database?

Question

I have an Access database on a network drive here at my company that multiple users are always in. I need all of them out of the database so that I can make modifications to some forms and reports. Instead of trying to find all of the users and making sure that they have exited out, is there a command I can use that will just kick them all out at once automatically? I have tried using the simple command of DoCmd.Quit, but it only kicked me out. Thanks for your help in advance.

Answer 1

Yes, it can be done, but there is not a single command that will do it all at once. You have to use a hidden form that has code in its Timer event so that it will periodically check a table which you can set a value to indicate that you wish to force all users to log off.



For example, I have a Access multi-user database using User-Level security. I have an "Administration" form that will display all current users logged in, and I can also click a button to initiate a forced log off. Let's say there are 3 users currently logged in. Within a few minutes, each user will get a popup warning on their screen that says the database will shut down. A few more minutes later, if they ignore the warning, the database will close itself. The users don't all get kicked off at the same time, but it will happen within about a 10 minute timespan. At the same time, when I've set the database for logoff, any new user attempting to open the database will get a message that the db is locked and they won't be allowed in.



This is all done programmatically, so if you are comfortable working with code, let me know and I'll send it to you.



By the way, the previous answer was correct in saying that Access is not really intended to used as a 24/7 database. Personally, I would've preferred to use a SQL database, however, where I work, my only software option was MS Access.

Answer 2

Access 2010 Multiple Users

Answer 3

An Access database is just a shared file, it's not an active DB server. There is no command to kick users from Access itself. To kick people out, you have to use the file sharing services on the server to close the user's file.



On the server, go to Administrative tools -> Computer management. On the left pane, open to Shared Folders, then click Open Files. You should see each person who has the mdb file open. From there you can forcibly close the file for each user.



Remember, this can cause missed updates if the a user is suddenly terminated before writes are flushed. Use this with care.



If you are having trouble with multiple users, it's time to move to a real multi-user database system. For example, you can buy SQL server or use the free and open source MySQL. Either system allows multiple users to see the data on the server and you can do things like live backups and force people off without losing data.



You can use Access as a front end, to display forms and reports while storing the data on the backend server. This way if you forcibly close the file, you are not screwing with your data store.



Since people are not closing the Access file, I can just about guarantee you are not getting backups of your database, which is dangerous. Access is good for trying things out and for a single user system and can be used occasionally for a couple of simultaneous users. It's purpose and design is not for a 24/7 multi-user database.

Answer 4

I am not a network person, but I did develop many Access apps for a company that I used to work for. I was CONSTANTLY making upgrades to the applications. We had front end/back end apps (which I would alway recommend). I would keep a copy of the ever-changing front end on my c drive (keeping the backend on the server) and then just copy the new front end out to the server when everyone was out But still it was impossible to find a time when EVERYONE was out. The network admin came up with a brilliant solution...she had me copy my revised apps out to the server and then had me run something (it's been years since I worked there, so forgive me that I cannot tell you what it was) and this would put my latest and greatest version each machine's c drive (as long as their machine was turned on). We found that having the front end on each machine's c drive caused less issues with crashes and what not. On the the application's main "switchboard" form, I had a "version number" (in a date fashion like 11.15.07) so I could tell what the last version was if someone was missing a feature. It worked very well for us.

Answer 5

hi, sorry to assert yet you're soliciting for issues doing this, as get entry to saves as you adjust any field settings, so the final individual to shop this is going to over write all the different persons, merely provide them "examine in basic terms" writes to repair this, desire this helps you.