By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,426 Members | 2,928 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,426 IT Pros & Developers. It's quick & easy.

Users Log in issue

P: n/a
I have a Question:
Can i Block all users from login more then one at the same time to my access
database?

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200605/1
May 31 '06 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Your goal is to make it impossible for more than one user to open the same
MDB at the same time?
May 31 '06 #2

P: n/a
no....
i have several computers in the office. what happend is that some people know
the user names and password of others in the office. so i would like to
prevent that if i loged in to the access under my user name
i don't want another employee to login the software under my user name at the
same time that i'm already log in to it.


Rick Wannall wrote:
Your goal is to make it impossible for more than one user to open the same
MDB at the same time?


--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200605/1
May 31 '06 #3

P: n/a
Easiest way:

Create your own table of users, with a field to note whether logged in or
not. Before opening the main app form, check the table. If that field
shows the current user is already logged in, bail out. If not, set the mark
and continue. Be SURE you have a way to clear that mark automtically on the
way out of the app. I keep one form open in hidden mode to take care of
this kind of stuff in its Form_Close event.

Why bother to have login/password if users know each other's passwords
routinely, if I may ask?
May 31 '06 #4

P: n/a
Considerations:

IF you take this approach, you will also need to have a backdoor into
that table that will allow you or someone to turn that flag off.

If the network goes down and the user loses connectivity, or if their
computer freezes up and they have to reboot. then they will still be
considered logged in and will not be able to get in FOREVER.

May 31 '06 #5

P: n/a
On 31-May-2006, "Ron2006" <ro******@hotmail.com> wrote:
Considerations:

IF you take this approach, you will also need to have a backdoor into
that table that will allow you or someone to turn that flag off.

If the network goes down and the user loses connectivity, or if their
computer freezes up and they have to reboot. then they will still be
considered logged in and will not be able to get in FOREVER.

OP: Read and heed!

You will need some admin screen that notices that you are you and lets you
(and only you) open the table or execute some code to clear out the table in
the case that Ron describes.
May 31 '06 #6

P: n/a
thanks for the info...

you idea is great. i did this solution before and that was the problem that i
had.

each time that the computer had to shot off, i had to log in and to update
the status.
by posting this issue i though that there is a better way to do it (without
the table) but now i guess that this is the only way.
again thanks alot for you time and information.
edan mimran

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200606/1
Jun 1 '06 #7

This discussion thread is closed

Replies have been disabled for this discussion.