[AccessD] Restrict # of User Logins to Access Part 3

Drew:

Your "little" Access 97 database that you "whipped up" (nice job of
whipping, I must add!!), works great....on the FE.  Each FE is on the users'
pc's.  Refreshed daily on startup/login.

However, I need to monitor who's logged into the BE, because there is only
ONE BE, but multiples of the FE all over the place, and the only place
they're (the users) all together is in the BE.  I'm trying to adapt your App
to use in the BE, but so far, no luck.  Might be just a brain phart on my
part, or I might be trying the ol' square peg in a round hole thing
(again...).

Is there a way to use your code in the BE to watch for multiple logins?
There is nothing in the BE except tables (no chairs...so ya have to
stand...<grin>)...

I suppose I could change it to hit the BE's ldb, but it's across the
network, on a mapped drive, and hence a little more vulnerable if something
in the network goes awry.

I hate to keep beatin' this up, but I'm not quite there yet.  Thanks for all
the input so far, too, everyone!!

Greg Smith
weeden1949 at hotmail.com


----- Original Message ----- 
From: "Drew Wutka" <DWUTKA at marlow.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Tuesday, August 19, 2003 12:19 AM
Subject: RE: [AccessD] Restrict # of User Logins to Access Part 2


Okay, goto my website (wolfwares.com).  There is a link on the Access
section (only link there), for Database Users.  It's a little Access 97
database I whipped up, which uses two classes.  One class is just a little
'property' holder, the other is the meat and potatoes, which builds a
collection of the first class, based off of both the user locks and the .ldb
file.  There is a form on the database, which shows the results.

Now, this thing DOES NOT use a special .dll, so the code can just be dropped
into place.

Enjoy (and forgive my bare site, still have had no time to work on it!
<Grin>)

Drew

-----Original Message-----
From: Greg S [mailto:weeden1949 at hotmail.com]
Sent: Monday, August 18, 2003 4:26 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Restrict # of User Logins to Access Part 2


Drew:

Yes, I think you're right...the .ldb file should be able to give me the
information I need.  However, I'm trying to use (as we 'speak' here) the
msldbusr.dll from JetUtils.exe (M$'s) and I can't get the dll registered.  I
could then pull the current users from the .ldb file.  Does this mean I have
to register it on all of their machines too?  Blech.  There has to be a
better way...

Is there another way to extract the users list from the .ldb?

And, Charlotte, btw, this is a "government" office...so there's no fear that
the locks "won't have time to clear" from when a user logs off to when they
log on again...<vbg>...

Greg
----- Original Message ----- 
From: "Drew Wutka" <DWUTKA at marlow.com>
To: "'Access Developers discussion and problem solving'"
<accessd at databaseadvisors.com>
Sent: Monday, August 18, 2003 3:41 PM
Subject: RE: [AccessD] Restrict # of User Logins to Access Part 2


No. And almost.  You have to have a bad crash to make the user lock stick.
In which case, making that one function work is not going to be the primary
concern.

Drew

-----Original Message-----
From: Charlotte Foust [mailto:cfoust at infostatsystems.com]
Sent: Monday, August 18, 2003 3:04 PM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Restrict # of User Logins to Access Part 2


But isn't there a delay in clearing out locks in the ldb file?  If they
shut down on one machine and went to another, is there any guarantee
that the lock would be gone?

Charlotte Foust

-----Original Message-----
From: Drew Wutka [mailto:DWUTKA at marlow.com]
Sent: Monday, August 18, 2003 12:02 PM
To: 'Access Developers discussion and problem solving'
Subject: RE: [AccessD] Restrict # of User Logins to Access Part 2


My solution to use the .ldb should work fine with the BE .mdb.

Drew