.LDB file: Is it the only source for user data? 1

[gusbrunston]

[tt]
Hi:

I have a procedure on a form to display who is logged on to the database. It reads the .LDB file and gives me the machine name but not the user name. Instead, it displays "Admin" where I'd like the user of the machine that is logged on. e.g., I'd like to see:

Machine User
FrontDesk Anastasia
Shipping Gregory
Billing Gertrude

Instead, I see:

Machine User
FrontDesk Admin
Shipping Admin
Billing Admin

I'm getting exactly what's in the .LDB file. Is there another source where I can pick up the name of the user that is logged on to the database?

Advance appreciation for your reading this post.

Gracias.

Gustavo[/tt]


[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[HitechUser]

gusbrunston,

Please have a look at this. It may help

http://www.mvps.org/access/modules/mdl0055.htm

..

 

[gusbrunston]

[tt]
Hi, Hi:

Thanks. I'll look into this thing.[/tt]




[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[gusbrunston]

Hi again Hi:

I've spent quite a bit of time on this procedure, and I've come a long way! As you can see, I'm almost there.

The shared database in on the machine named "FASTGUS".

The only entry that shows the user name is from a Windows 2000 client (named DELLGUS). All the other machines are Windows XP Pro.

Might you be able to direct me to any changes necessary to display the user name in Windows XP, if indeed that is the problem?

Thanks so much,


[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[MichaelRed]

The ".LDB" file can only return the "log on" info from Ms. A. Security. If you haven't set up user / group level security, they all just say Admin. and can never be anything else. Depending on the Network set up, you might be able to get eh network's user name, but not via the .LBD





MichaelRed

 

[gusbrunston]

[tt]
Hi, Michael:

The White Paper that HiTechUser suggested, has 39 or so pages, and I haven't read them all. But I read enough to see some mention of "extended range" in the .LDB file. This is all predicated on using a MSDB (?) library file called "jetutils.exe" (which took me a little doing), which includes a form "frmLbdViewer", which is how I got the image above.

Anyway, I did get a user name...in the image above, the user on machine "DELLGUS" is a user named "midoffice". Thus, "DELLGUS\midoffice" is a satisfactory result, but I only get it from THAT box--one with W2000 Pro rather than WXP Pro.

I guess I can study that 39 page white paper, but I was looking for an easier, softer way.

Thanks very much for your attention to my post.[/tt]

[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[gusbrunston]

[tt]
Again, Michael:

The user name is stored in another location used by this form: in something called "Jet 4.0 UsersRoster".

You were right, of course.

I have confirmed that my form works with Windows 2000 but not with Windows XP. So I've narrowed my problem down, anyway.

Thanks again.[/tt]



[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[HitechUser]

Gus,

Sorry a bit tied up. Anyway these may help.

ViewUser

or this.. (I think you might have this)

http://support.microsoft.com:80/support/kb/articles/Q176/6/70.ASP&NoWebContent=1]Microsoft[/url]


Let me know if you find a solution...

 

[gusbrunston]

[tt]
Hi:

I have confirmed that the LDB Viewer I'm using only works with Windows 2000 and Windows NT.

I'll try the two links you just gave me.

Thanks again,[/tt]

[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[willir]

Note:
The "Admin" login is the default login for Access.

Have you considered implementing user / groups security?

Richard

 

[MichaelRed]

All ver '98 Win and later (at least) can / do have the local user name avaialble if there is any (WIN) logon. This is the reference I meant for the Net gurus. If you have the a network, there is the simple possability that all users CAN be asked to use the machine log on, which is then available. There is also the possibility that the net guru's can REQUIRE a network log on which is also available. Either of these would provide an alternative to the Ms. A. Security log on which includes that name in the LDB file.

Please note that NONE of the above is all that reliable. The first (Win machine log on) is easily bypassed (at least up through ver '98. All become somewhat suspect unless there is a relatively brief inactivity log out associated with the individual log on. Many (individuals) resent the necessity to continually log back onto their 'domain' (machine | network | application) and often win the arg to be required to do so. When this occurs, the real user may easily be someone other than the current logged on user. In the case of the Ms. A. security, hte situation can be even more of an issue, as any inactivity time out / log off needs to consider the specific situation re data entry/edit and what to do about a partially entered or 'in Edit' record = should the (and if so -HOW) to save the changes.





MichaelRed

 

[gusbrunston]

Hi Michael:

I have postponed for years learning what I should know about database security. Maybe 2005 is the year.

Thank you for your comments.

Sincerely,

[tt]
Gus Brunston - Access2000/2002(DAO)[/tt]

 

[Grandkathy]

Hello,

I've been reading and reading trying to get this function figured out. thanks to all of you in here, I've got it working beautifully.

HiTechuser, I went to the ViewUser page and this is the first one that's worked so easily and well for me. Thanks.

Now, I have another question regarding this.

When the information is retrieved in the text form, is there any way to have it appended into a table in my database?

i've named a table tblDatabaseUserInfo, with fields named exactly as they come up in the text field: Computer name, Login Name, Connected, Suspected state.

Thanks again for all your help.

Kathy

 

[MichaelRed]

" ... in the text form, is there any way to have it appended into a table ... "

I am not trying to demean you or your abilities, but the question itself demonstrates a relatively low level of knowledge / understanding of the subject. "WYSWIG" inherently implies more-or-less what the acronym stnds for. Of course, that doesn't (necessarily) make it easy for the novice, in that there may by different levels of "seeing" it. I haven't used the "addin", and therefore do not know the specific details of it. In the general sense, MS. A. is an "interperted" program, so the 'source' objects are all available for the user to modify (depending on security settings) at will. This, in turn, implies 'knowledge' (or at least the possability) of knowledge of the inner workings. What the 'viewer' is doing is (in a simplistic sense' is simply reading a (text) file, interperting the content and displaying some portion on a form. If, the form is available for view in the 'design' mode, you can read the design details, including the 'control source' of the relevant text boxes (if they is are bound controls) or peruse the code to see how they (the controls) are populated. Once you know how the controls are populated, you then have their content to do with as you like - including appending to a table of your own.

Having 'walked' through the concept, will (I suspect) NOT readily answer your question, but (perhaps) raise a few new / additional ones. Please feel free to use the ubiquitous {F1} on some of the terms which raise those questions. After having done some of this 'homework', please feel free to open your own thread(s) with requests for further help.

If, on the other hand, the "addin" is not available to you in the 'source' format, I would suggest a visit to your local bookstores' computer section for a review and purchase of a third party tutorial on Visual Basic &/or Ms. Access. To persue this specific topic, one of the tomes should include a discussion of the ".LDB" file. Several authors have explored this obnject in sufficient detail for most to be able to abstract the relevant parts of hte code for their own usage.





MichaelRed