Password system creation for shop floor Machines integrating MSAccess barcode system

[santhosh23]

Hi ..

I have created a system in Access for Assigning work to employees. I had used Barcodes [123456789011] for Employees,Project , Activity,Machines. Now I am planning to build a system in which when I assign work for an employee and a Machine. Only the particular employee can access that machine at that time. I am planning to use an Password system in Machine , so that when the employee scans his identity card he should give the password to access the machine. The entire logic is to avoid employees using machines of their own and unwanted entry in the machine. Have anybody built something i this?? and also I need info on the Password System to use whether to use a door entry system or id password card reader etc..

any help is appreciated..

 

[Ranman256]

similar. I had a table of users, tUsers. It has their userID. It would read it from their PC logon, but yours would lookup the badge ID in the same table.
Then connect to the tSchedule table to see if their badge is scheduled.

Upon badge scan the text box txtLogin would fill then run to see if it is valid.

dim bIsValid as boolean, bIsSched as boolean

bIsValid = Dlookup("[Enabled]",[tUsers]","[Badge]='" & txtLogin & "'"

if not bIsValid then
     'you could post invalid entry record here
   msgbox "Not valid Badge" 
   docmd.quit
end if

bIsShed = Dlookup("[Badge]",[tSchedule]","[Badge]='" & txtLogin & "'and #" &  Time() & "# between tSchedule.StartTime and tSchedule.EndTime and [Machine]='" & txtMachine & "'")

if not bIsShed then
     'you could post invalid entry record here
   msgbox "Not scheduled for machine:" & txtMachine
   docmd.quit
end if

 

[santhosh23]

@Ranman256 .. thanks for the information . So In this code you are checking for 2 level of authorization
(I) Whether the user has access to machine
(II) whether the user is scheduled to do the work in the machine..

Any idea on how to display this info in CNC Machines. Because I want this program to be in Machine ( or a device attached to machine) and not in computer.

 

[Ranman256]

oh, dont think access works anywhere but on PCs.
I thought you had the PC connected to the machine to monitor usage.

 

[santhosh23]

@Ranman256 ..

Hi ..thanks for the info. Yeah i understand that but what i was looking is a device attached with machine which should have password entry to unlock the machines. the user will be given password to work in machine. only when the password matches with program in device it can be unlocked..I am thinking of this to eliminate the unwanted access of machine in workshop and to secure the machines..

 

[GPGeorge]

@Ranman256 .. thanks for the information . So In this code you are checking for 2 level of authorization
(I) Whether the user has access to machine
(II) whether the user is scheduled to do the work in the machine..

Any idea on how to display this info in CNC Machines. Because I want this program to be in Machine ( or a device attached to machine) and not in computer.

Ranman256 is quite right. You are trying to mix apples and oranges, unless this CNC machine has a Windows Operating System and you have Access installed on that Windows OS on that machine, of course. And that doesn't sound like it's the case.

In fact, the original requirement, " I am planning to use an Password system in Machine , so that when the employee scans his identity card he should give the password to access the machine" has nothing to do with MS Access, the relational database application on a computer. If the CNC Machine itself is password protected, then that's where you have to implement your security procedure.

"... what i was looking is a device attached with machine which should have password entry to unlock the machines."

Again, a device attached to the CNC machine would be a piece of equipment designed for that purpose, would it not? Does the vendor of your CNC Machines provide such devices? Can you even find a third-party device to do that? Can you program something in Windows to do that?

So far as I can tell, this is not an MS Access problem, as intriguing as it may be as an automation project in its own right.