Command upon Exit

[Novice1]

I've asked this question before but I usually get the same response (create a user table) but this isn't quite what I'm looking for.

I don't want people to log in as they open a db. I want to limit the number of machines (10) using the dbs.

I have a small collection (12) of DBs (split). I don't want more than ten operators at a given time.

I can create a table in the backend linked to the front end dbs (showing the number of people of logged in).

I initially thought ... limit the table to 10, create 10 logged in fields (Y/N). When the first user logs in change field1 from no to yes. When the next user logs in, check field1 (if yes change field2 to yes) and so forth. I believe this will work; however, if the same user opens another db, that user will be logged in as a second user (which I don't want).


I want to limit the number of machines/people. These people should be able to open one or more of the dbs.

Instead of having one table, I suppose I could create this table for each of the dbs. This would probably work. I would prefer to have one table for all the dbs.

I have a simple brain. Please help

 

[Uncle Gizmo]

I suspect the real issue is not logging in, its logging out. People don't always log out properly. If they don't use the correct log out procedure, then the backend will not know they have logged out. You could have somebody who has logged in, shut down Access incorrectly, still looking like they are logged in, therefore blocking someone else using it. The next issue is you could have someone who is logged in but they don't use the database. They go off for tea break or to a meeting, leaving the database logged in. Again, blocking a legitimate users access to the dB... So I think you might need to do a little bit of deeper thinking into the issues.

 

[gemma-the-husky]

have a user slot table that puts the user name in the next slot.

check the slot table to see if a new user is already logged in, and thereby prevent him having multiple log ins.

you can use a version of this to control access to multiple databases.

as Uncle Gizmo says though, you simple HAVE to have a facility to clear a slot that has remained locked in error.

 

[Bolloc]

This may be a quick and dirty solution but Win XP Pro only allows 10 concurrent connections to it, so could try to host it on there?