LOCK a form so no one else can use it until 1 user is finished

[TomKat]

Hi all,

I have a form that is constantly used by several people at the same time. I would like to be able to have one user have the form open, and lock others out from using it until the one user closes it.

When the one user does have it open, and someone else tries to open
it. I would like a msgbox to inform the user trying to open it that it is currently in use and must wait. Then when closed, inform them that it is free.

I am currently using this (=FOSUserName()) in a text box to display
the current users name when they have it open. I am thinking that
it could be used somehow to send the msgbox to the person when the
form is available.

Thanks for all your help.

 

[gemma-the-husky]

this sounds like you have not split your database properly

you should NOT all be using the same (networked) copy of the dbs

 

[TomKat]

I have split it correctly, just it is still residing on the network until I get the tweaks that I want done. Then I can have everyone copy the front end to their desktop. So what your are saying is that.... if they had their own copy, it would be used by just that person where the front end resides?

 

[georgedwilkinson]

Yes, when you split a DB, each user gets their own copy of the front end which runs in their own memory space in their own processor. The tables are locked by Access as needed so you shouldn't have any problems with that.

 

[TomKat]

Great, so when I get done tweaking the things I need. And finally finished .. I will have them copy it over their desktop.

 

[gemma-the-husky]

the thing is

a) you will struggle to change things if/while other users are using the dbs
b) you are increasing the chances of corruption if multiple users are sharing the dbs

 

[TomKat]

a) Yes I am aware of that and is why I work on it at nite when it is not in use.
b) At most, there are two or three at a time using it.

Why I need to get this done. I had not choice but to get what I had out and into
use at the time. Now based on input for requests to do this or that, or change
this or that. I am still fine tuning it with VB.

 

[gemma-the-husky]

you are probably better developing with a copy of your own, then release the new version to the shared environment from time ot time

keep copies/backups of your released versions for when you get corruptions!

you have split the data from the code haven't you?

 

[TomKat]

It is backed up daily and I work on a copy on my desktop.

split the data from code?

data is on a backend "named_be.mdb"; queries, forms, etc in the other front end.