Users sharing a Computer & Access

Users sharing a Computer & Access - What's the answer?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Will - 16 Nov 2005 15:51 GMT

I have a client who is a manufacturer and an Access application is used down
on the shop floor where they have PC's in each production area. Currently
when a transaction is entered the worker just selects their name from a drop
down list but the problem with this is that they can select any name not
just their own. There is currently a generic login for each PC e.g. Line1,
line2. Access security is not in place. As I see it my options are either
to implement Access Security/Security at Logon where each shop floor worker
has a username and password and everytime a user finishes their transaction
they must exit the access application or I have a transaction based system
where each time they carry out a transaction they enter their username and
password stored in "in house" security table to verify themselves. Does
anyone have any other suggestions or examples of similar situations?

thanks

Reply to this Message

Brendan Reynolds - 16 Nov 2005 17:02 GMT

Use Windows security - it can be configured to lock the PC and require the
user to log-in again after a period of inactivity. There's code in the API
section at www.mvps.org/access to retrieve the user-name of the logged-in
user for use in your Access app.

Signature

Brendan Reynolds

>I have a client who is a manufacturer and an Access application is used
>down on the shop floor where they have PC's in each production area.
[quoted text clipped - 11 lines]
>
> thanks

Reply to this Message

Will - 17 Nov 2005 11:47 GMT

Thanks for your reply
I had thought of this but this would mean users having to log off/log on, on
every transaction. I'd be interested to hear if other people are faced with
this problem and how they deal with it

> Use Windows security - it can be configured to lock the PC and require the
> user to log-in again after a period of inactivity. There's code in the API
[quoted text clipped - 16 lines]
>>
>> thanks

Reply to this Message

Rick Brandt - 17 Nov 2005 12:56 GMT

> Thanks for your reply
> I had thought of this but this would mean users having to log off/log on, on
> every transaction. I'd be interested to hear if other people are faced with
> this problem and how they deal with it

You could give the employees bar-coded name tags and have them scan in their ID.
The TextBox that you scan into could use the Password InputMask making it
difficult to attempt hand entry.

Signature

I don't check the Email account attached
to this message. Send instead to...
RBrandt at Hunter dot com

Reply to this Message

Will - 17 Nov 2005 15:16 GMT

Very interested in this approach - Thanks for the idea
Correct me if I'm wrong but I imagine it working much like a bar worker and
operate within Access like this:
tblEmployee, which would include EmployeeID, EmployeeName &
EmployeeBarCodeID. The application would open with a main login screen with
a form with a textbox (password entry as you say), & with the cursor in the
textbox, the shopfloor worker scans their card over the barcode reader and
then clicks on an enter button. This then DLookup's their EmployeeID & this
is then stored as a Global variable or in a temporary table. Once they have
completed their transactions they click log off, returning the screen to the
login prompt. Anyone have any input or better suggestions?

thanks for your help

>> Thanks for your reply
>> I had thought of this but this would mean users having to log off/log on,
[quoted text clipped - 4 lines]
> their ID. The TextBox that you scan into could use the Password InputMask
> making it difficult to attempt hand entry.

Reply to this Message