Single User Database

[Paul H]

I need to answer a simple question just put to me. Another department has a database designed for a single user at one time. When one person is using it, everybody else needs to stay out. All I need to know is either how to keep more than one user from using the database at a single time or have the database bark at them instead of them barking at each other, which is apparently how they are doing it now. Even better would be to tell them which user is in the database so they could politely request the user to get out.

[JeroenMioch]

Make a new table with one field in it. In the field you put "LoggedOut"

When someone logs into the system you make a SQL update that changes the value "LoggedOut" to "LoggedIn".
When someone leaves the system you let another SQL update change it to "LoggedOut".

If someone else opens the application, you check the value of the field with Dlookup.
Off course when the Dlookup returns "LoggedOut" you let them enter the application by code that loads the form.
When the value is "LoggedIn" you return a messagebox "A user is currently using the application" and exit the application using code.

This is very basic stuff, but you can even let the system send an email as soon as someone logs off

[ItsMe]

When the db opens you could have it search for an laccdb file in the db directory.

[Paul H]

Thanks Jeroen. I like simple.

Also thank you ItsMe. It's always nice to have a backup plan.

[JeroenMioch]

Tomorrow i am at work and could provide you with the codes if you like

Glad to be of help

Greetings: Jeroen