Sign-In type Access Application

S

SludgeQuake

Very new to Access.
Is there a way to simulate a log-in process in access? We currently log in
to our PCs using group log-ins. (log in names are our general job titles,
operator, supervisor, TCA, etc.) So it won't help to reference the
application user name.
An ideal function would automatically log out at shift change times (6 AM, 2
PM, and 10 PM) to avoid operators "riding" the log-in of the previous shift.
I'm working on an e-log for tracking events at our plant.
The form used currently has a cbo for employee ID (though he would only see
his name). If he were somehow logged in, ideally with a password, then that
would be one less entry (and one less chance for mishap).
I'm hoping someone can give me a reference for this type of application,
unless there's a relatively simple approach.
Thanks,
Sludge
 
K

Keith Wilby

SludgeQuake said:
Very new to Access.
Is there a way to simulate a log-in process in access? We currently log in
to our PCs using group log-ins. (log in names are our general job titles,
operator, supervisor, TCA, etc.) So it won't help to reference the
application user name.
An ideal function would automatically log out at shift change times (6 AM,
2
PM, and 10 PM) to avoid operators "riding" the log-in of the previous
shift.
I'm working on an e-log for tracking events at our plant.
The form used currently has a cbo for employee ID (though he would only
see
his name). If he were somehow logged in, ideally with a password, then
that
would be one less entry (and one less chance for mishap).
I'm hoping someone can give me a reference for this type of application,
unless there's a relatively simple approach.
Thanks,
Sludge
Click to expand...

User-level security is a built-in function in Access that would suit your
needs by the sound of it. The downside is that there's a steep learning
curve and plenty of scope for mistakes. If you do opt for ULS then start by
following the steps in the MS FAQ (link on my web site) on a COPY of your
database (always use a copy in case you lock yourself out).

If you want to log users out automatically then this is something that you'd
have to code into your app yourself. It is possible, I've done it myself.

HTH - Keith.
www.keithwilby.com
 
S

SludgeQuake

I've scanned the info on the web site. It looks like a good way to go -
particularly for another application I'm working on tracking employee
sick/vacation time. But being new to Access, I need to learn the basics of
database development first. I'll tackle the steep learning curve for the ULS
after I gain more experience developing Access applications.

Maybe for the e-log, I'm shooting too high to try to use passwords. My
MS-Access skills are so poor, I'm afraid this might be a dumb question, but
I'm thinking of an approach that might look something like:
- have a log-in form
- time stamp the log-in along with the employee ID
- query the log-in table to select the name associated with the latest time
stamp
- set the default on the operations log entry form based on the query
- somehow cue the operator to re-log in if the time stamp on the log file is
older than the last shift change. (perhaps before they try to call up the
form to enter a new event?)

I like the idea of a password; and I think in the future it would be the way
to go. But for now I'm not sure if I want to do too much to "strongarm" the
operators to logging in correctly. (We're currently using Excel spreadsheets
for our electronic logs... The operators simply use the data validation drop
down to enter their name in the appropriate column. Anything we might set up
in access will likely improve this part of our tracking.)

Sludge
 
J

John Spencer

Simple method to identify people, but that will not really impose any
security.

Add a table StaffTable
Fields
--UserID - Text
--UserPassWord - Text (apply Password Input Mask)

Open an unbound form have the user input the UserID and Password into
unbound controls. Then have them press a Login button that will validate
the userid and password. If it passes validation, then open your main entry
form, otherwise advise them of the problem.

Validation could be as simple as
IF IsNull( DLookup(""UserID","StaffTable","UserId=""" & Me.txtUser & """ AND
UserPassWord=""" & me.txtPassWord & """") ) then
Msgbox "Incorrect login"
else
Me.Visible = False
DoCmd.OpenForm "Your Main Form"
end if
 
C

chris.nebinger

Personally, I'd have more concerns about logging into the network via
group logins rather than personal ones. From a security standpoint,
that issue is a serious one. If they logged in via their network
login, with screensavers set to come on in 10 minutes, and password
protected, then you could use the network ID as the employee
identifier.


Otherwise, the above directions all look good.


Chris Nebinger
 
Top