Preventing Double Login

[Nick]

What I would like to do is if user Fred is already logged in on Computer1
into Test.mdb with Secured.mdw, I don't want him to also be able to log into
computer2 into Test.mdb with Secured.mdw as Fred.

What I am trying to say is, after security is setup, a person can log in
once, which is fine, I want them to do that of course, but if they try to
log in to the same database from another PC, a message will appear which
says something like, "Sorry buddy, you are already logged in on Computer1,
you can't log in here or anywhere else until you log out of PC1." How do I
stop someone logging in twice using the same user name? Even if there are
twenty different registered users all logged in simultaneously each tapping
away doing their thing, none of them should be able to log in again on
another PC if already first logged in.

I've been reviewed a couple of articles on the MSDN site which covers
identifying who is logged in ( Identifying Users
http://msdn.microsoft.com/library/en-us/odeopg/html/deovridentifyingusers.asp
and
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnimo01/html/o2k0135.asp)
but they don't quite go far enough.

Can anyone provide specific help here please?

Thanks
Nick

 

[TC]

In Jet 4 (Access 2000+) there is a UserRoster thing that (I believe) will
tell you who is currently logged-in. And the CurrentUser() function tells
you the name of the current user. Maybe you could use those things together
in your startup code, to see if the current user is already logged-in
somewhere else.

In Jet 3 there is no UserRoster thing. But there was a freely-distributed
DLL that did a similar thing. I can't remember what it was called, but some
googling should find it, or maybe someone else will advise.

HTH,
TC