Active Directory

[Markus]

I would like to tie in logins for my app to Active Directory to make it
easier to set up privileges for logins. Have read some things about AD, but
cannot find something that gives me specifics on how I might use it in this
way.

I now have a standard system, storing privileges for each user in a table
that is read at login. Can this info be tied in to AD in some way to make
user setup easier?

Thanks for any and all ideas on this,
Mark

 

[Arvin Meyer [MVP]]

You can get the Window Login Username from:

http://www.mvps.org/access/api/api0008.htm

 

[Markus]

Arvin,

That's interesting. Could you tell me if I am on the right track here.

For example, I could store the network login name in a field in the same
table I use now for user privileges for my app. Then when the user clicks on
the icon to run my app, I could obtain the users network login name, locate
that user record in my user table, and in that way I could bypass a separate
login screen for my app.

Is that correct?

This would be very cool.
Thanks,
Mark

 

[Tony Toews [MVP]]

For example, I could store the network login name in a field in the same
table I use now for user privileges for my app. Then when the user clicks on
the icon to run my app, I could obtain the users network login name, locate
that user record in my user table, and in that way I could bypass a separate
login screen for my app.

That is correct.

However any home made security that Access can provide can be bypassed
by the user simply taking the Access data MDB home with them.
Whereupon they can go through the data themselves using a retail copy
of Access.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Arvin Meyer [MVP]]

However any home made security that Access can provide can be bypassed
by the user simply taking the Access data MDB home with them.
Whereupon they can go through the data themselves using a retail copy
of Access.

That's very true. Or even with Excel, if they have the driver. In addition
to obscurity, which is never really adequate, one must make sure that users
do not have the means to get to and/or copy the data. Only a server can
truly protect data. In the end, all security depends upon the honesty and
cooperation of employees.