Locking Out Users

[Guest]

For a timesheet application, I would like to both:

- prevent project managers from loading the Timesheet form if the principal
is processing billing (which is based on totals of current records) and
- prevent the principal from loading the billing form if any project
managers are entering their timesheets

Can anyone help?

Thank you.
Sprinks

 

[Rick B]

I would probably add a flag to a table that is set by code in your forms.
When the principal starts processing (however that is done) set a flag.
When the project manager is entering time, set a flag.

Then, in the form that opens with the database, check those flags and close
the application if they are not in the desired status. This form would have
to look at who was logged on and would have to know if they were a manager
or a principal in order to check the appropriate status flag.

 

[Guest]

Rick,

Thank you; I think this approach will work.

It does, however, leave a small window if these two forms are being loaded
almost simultaneously by different users. Do you know how I could allow only
one user at a time by default, then set the appropriate flag, and THEN revert
back to multi-users? That way, I know for sure that the flag is set when a
second user comes online.

Thank you.

Sprinks

 

[Rick B]

I don't, but perhaps one of the MVPs will jump in.

 

[Ed]

Multi-user to me means one back-end .mdb and a front-end .mdb for each user.
Then set the 'flag' in a one-record table by the current user that will lock
out all others.
Ed

 

[Guest]

Thanks for your response, Ed.

Sprinks

Multi-user to me means one back-end .mdb and a front-end .mdb for each user.
Then set the 'flag' in a one-record table by the current user that will lock
out all others.
Ed