Hi, Jonathan.
Here's a tough one for ya. I want to . . . take the SSN field and use that
as the user accounts' password.
Here's reality for ya: storing people's SSN's in an Access database can get
your company into legal hot water. Anyone determined enough can steal those
SSN's and any associated Employee ID's, names, et cetera, that are stored in
the Access database. (Even if there are no names, the Employee ID's can
probably be cross-referenced in other databases or on paperwork with
employee names.) If this person doesn't have the skills, it doesn't matter,
because the tools are available very inexpensively.
Think it can't happen to your company? The latest surveys show that 30% of
Americans who use the Internet have been victims of identity theft. Don't
give a disgruntled employee or an outside hacker the opportunity to steal
anyone's SSN. The chances are too high that someone eventually will.
take the emp# field and create a new user account in my frontend
database and then take the SSN field and use that as the user accounts'
password.
Again, don't store and use anyone's SSN, so use something else for the
passwords. You can view sample code for creating a new user and joining
that user to a group in section 38 in the Security FAQ on this Web page:
http://support.microsoft.com/default.aspx?scid=/support/access/content/secfaq.asp
Make sure that the code is running while the user is joined to the same
workgroup used to secure the front end database. Otherwise, the new user
will become a member of the workgroup that the current user is joined to.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)