Prevent two people from signing in at same time using the same logininfo?

[eighthman11]

this is probably very simple but I don't know. Is there a way to
prevent two people from signing
on to an Access Application using the some login information????

I can't have two people on the application at the same time with the
same user name. I use currentuser for some locking and filtering.

Thanks for any help.

ray

[Fred Zuckerman]

"eighthman1 1" <rd******@noote r.comwrote in message
news:b5******** *************** ***********@w28 g2000hsf.google groups.com...

this is probably very simple but I don't know. Is there a way to
prevent two people from signing
on to an Access Application using the some login information????

I can't have two people on the application at the same time with the
same user name. I use currentuser for some locking and filtering.

Thanks for any help.

ray

Two suggestions:
1. Provide a unique username/password to each user and tell them not to
share.
or
2. Create a table and store the field CurrentUser() as each person logs in.
Then delete the record when they exit the database. If the record already
exists when somebody logs in, then give them a msg and docmd.quit

Fred Zuckerman

[Arno R]

"Fred Zuckerman" <Zu********@sbc global.netschre ef in bericht news:Es******** **********@news svr13.news.prod igy.net...

"eighthman1 1" <rd******@noote r.comwrote in message
news:b5******** *************** ***********@w28 g2000hsf.google groups.com...

>this is probably very simple but I don't know. Is there a way to
prevent two people from signing
on to an Access Application using the some login information????

I can't have two people on the application at the same time with the
same user name. I use currentuser for some locking and filtering.

Thanks for any help.

ray

Two suggestions:
1. Provide a unique username/password to each user and tell them not to
share.
or
2. Create a table and store the field CurrentUser() as each person logs in.
Then delete the record when they exit the database. If the record already
exists when somebody logs in, then give them a msg and docmd.quit

Fred Zuckerman

Also, when using suggestion 2, provide a way to 'clear' the CurrentUser-login record !

This is really needed, because at times they will *not* log out the proper way. (e.g. crash or network failure)

You could create a macro 'DiscardCurrent UserLogInRecord ' to do the following
--Let them in (don't write a record when the record exists) or...
--Clear the record and quit (so they can log in again the usual way)
You would need another shortcut with the /x switch to run the macro.

Arno R

[Salad]

Arno R wrote:

"Fred Zuckerman" <Zu********@sbc global.netschre ef in bericht news:Es******** **********@news svr13.news.prod igy.net...

>>"eighthman1 1" <rd******@noote r.comwrote in message
news:b5****** *************** *************@w 28g2000hsf.goog legroups.com...

>>>this is probably very simple but I don't know. Is there a way to
prevent two people from signing
on to an Access Application using the some login information????

I can't have two people on the application at the same time with the
same user name. I use currentuser for some locking and filtering.

Thanks for any help.

ray

Two suggestions:
1. Provide a unique username/password to each user and tell them not to
share.
or
2. Create a table and store the field CurrentUser() as each person logs in.
Then delete the record when they exit the database. If the record already
exists when somebody logs in, then give them a msg and docmd.quit

Fred Zuckerman

Also, when using suggestion 2, provide a way to 'clear' the CurrentUser-login record !

This is really needed, because at times they will *not* log out the proper way. (e.g. crash or network failure)

You could create a macro 'DiscardCurrent UserLogInRecord ' to do the following
--Let them in (don't write a record when the record exists) or...
--Clear the record and quit (so they can log in again the usual way)
You would need another shortcut with the /x switch to run the macro.

Arno R

Also, maybe get the Machine name.
http://www.mvps.org/access/api/api0009.htm

Using LDBView or JetRoster or whatever you can determine who is in the
system. Comparing the machine names to a table can help. If Joe left
the app by crashing and burning, he would not exist so any records of
him in a table could be removed so he could log in.

[eighthman11]

On Dec 4, 12:25 pm, Salad <o...@vinegar.c omwrote:

Arno R wrote:

"Fred Zuckerman" <Zuckerm...@sbc global.netschre ef in berichtnews:Es* *************** **@newssvr13.ne ws.prodigy.net. ..

>"eighthman11 " <rdshu...@noote r.comwrote in message
news:b5******* *************** ************@w2 8g2000hsf.googl egroups.com...

>>this is probably very simple but I don't know. Is there a way to
prevent two people from signing
on to an Access Application using the some login information????

>>I can't have two people on the application at the same time with the
same user name. I use currentuser for some locking and filtering.

>>Thanks for any help.

>>ray

>Two suggestions:
1. Provide a unique username/password to each user and tell them not to
share.
or
2. Create a table and store the field CurrentUser() as each person logs in.
Then delete the record when they exit the database. If the record already
exists when somebody logs in, then give them a msg and docmd.quit

>Fred Zuckerman

Also, when using suggestion 2, provide a way to 'clear' the CurrentUser-login record !

This is really needed, because at times they will *not* log out the proper way. (e.g. crash or network failure)

You could create a macro 'DiscardCurrent UserLogInRecord ' to do the following
--Let them in (don't write a record when the record exists) or...
--Clear the record and quit (so they can log in again the usual way)
You would need another shortcut with the /x switch to run the macro.

Arno R

Also, maybe get the Machine name.http://www.mvps.org/access/api/api0009.htm

Using LDBView or JetRoster or whatever you can determine who is in the
system. Comparing the machine names to a table can help. If Joe left
the app by crashing and burning, he would not exist so any records of
him in a table could be removed so he could log in.- Hide quoted text -

- Show quoted text -

Thanks to everyone who replied. Sorry I didn't get back with you
sooner; I was sent out of town for work.
I ended up doing Fred's idea of keeping track who is signed in by
currentuser(), it worked great. Thanks
again to everyone.