security not for security

  • Thread starter Thread starter Daddio
  • Start date Start date
D

Daddio

I don't want to have to set up everyone's security stuff
yet. I know enough to know that no one here has enough
expertise to really do it right. I only want a form to
know who is entering data, and to do something different
for different users. Is the Access security log-in what-
cha-ma-call-it the only way for it to know? Or can Access
tap in to some Windows features or Outlook ID or something?
Obviously I'm no expert, so don't chastise me for that.
Feel free to talk down to me, though. OK, please talk
down. I don't speak SQL or code very well. (Why am I
doing this?) ;-)
Thank you for the help!
D²
 
I don't want to have to set up everyone's security stuff
yet. I know enough to know that no one here has enough
expertise to really do it right. I only want a form to
know who is entering data, and to do something different
for different users. Is the Access security log-in what-
cha-ma-call-it the only way for it to know? Or can Access
tap in to some Windows features or Outlook ID or something?
Obviously I'm no expert, so don't chastise me for that.
Feel free to talk down to me, though. OK, please talk
down. I don't speak SQL or code very well. (Why am I
doing this?) ;-)

If the users are logging onto an NT network you can use code at the link
below to retrieve their network UserName.


http://www.mvps.org/access/api/api0008.htm
 
This might be the easiest way.

(1) Use Tools : Security to create some new users ("Tom", "Jane Jones",
whatever). Also add a password to the Admin user. Now, everyone who runs
your database will be required to enter a valid username/password. Apart
from Admin, all the passwords willbe blank, by default.

(2) Put a textbox on your form. Set the controlsource of that textbox to:
=CurrentUser()

Now, when a user opens that form, they will see their logon name in the
textbox. That's a start, at least!

Be aware that this will cause *every* database to ask for a
username/password. To restrict the effect to just one database, you will
have to learn about the "workgroup administrator" program, and how to create
shortcuts to open your database with a selected workgroup file.

To remove the need for everyone to log on with a username/password, just
delete the password from the Admin user, then everything will go back to
normal.

HTH,
TC


I don't want to have to set up everyone's security stuff
yet. I know enough to know that no one here has enough
expertise to really do it right. I only want a form to
know who is entering data, and to do something different
for different users. Is the Access security log-in what-
cha-ma-call-it the only way for it to know? Or can Access
tap in to some Windows features or Outlook ID or something?
Obviously I'm no expert, so don't chastise me for that.
Feel free to talk down to me, though. OK, please talk
down. I don't speak SQL or code very well. (Why am I
doing this?) ;-)
Thank you for the help!
D²
 
The way I dealt with this was to create a form that opens
up automatically via AutoExec Macro (openform..) and have
people "log" in. You can create a user screen just like
the ones in xp with a button for each person... or you can
have a drop-down combo box list the users' names and they
can select their own name and then you can have a field
that they enter their password in. You can use Global
varialbes to hold their name, user ID, or whatever. That
variable can then populate various fields which keep track
of who is entering what data. Or... you can have a form
look to who is logged in on the log-in form and populate
forms that way (ie. OnCurrent of the Form: Me![User] =
Forms![LogIn]![Name]. This causes a control on a second
form, which could be invisible or just DisEnabled, to
automatically populate with the person logged-in when the
second form opens.

Of course this doesn't prevent someone from going behind a
form directly into a table and changing the data! But you
can make it difficult for them to do this by various easy
security measures.
 
Back
Top