login page (2 Viewers)

[Johanvdw]

Guys, thanks to a member (charles), who helped me developed a nice delivery note system, I would love some help to add a login system to it. When an employee are logged in, his credentials(username, tel no and signature) must automatically added onto the reports(Delivery note & gatepass). Can somebody help me with this?

 

[Pat Hartman]

Here's a sample Switchboard with simple security.

Switchboard with simple security

This is a custom switchboard. It expands on the Switchboard Items table to add four additional columns to define view/edit/add/delete security levels for switchboard items and forms/reports referenced by them. It includes tables to manage users and also to assign them security levels. The user...

www.access-programmers.co.uk

If all you want is the login, you don't need to worry about the other stuff.

 

[Ken Sheridan]

When an employee are logged in, his credentials(username, tel no and signature) must automatically added onto the reports(Delivery note & gatepass).

Rather than closing the login form once a user has successfully logged in, hide it by setting its Visible property to False in the form's module. You'll then be able to reference controls in the login form from other objects. In the attached little demo file the user logs in and enters a hashed password. If they then open either of the bound forms their user name and permissions to the form are shown in unbound controls in the form header.

 

[Isaac]

Guys, thanks to a member (charles), who helped me developed a nice delivery note system, I would love some help to add a login system to it. When an employee are logged in, his credentials(username, tel no and signature) must automatically added onto the reports(Delivery note & gatepass). Can somebody help me with this?View attachment 121852View attachment 121853View attachment 121854

Do your employees each work under a unique network login? If so, just grab that information and put it all in a table with various other attributes as needed. Then use (any one of multiple methods) to get their logged-in network username at runtime and look up their permissions from the table. such as Environ(username)

 

[Gasman]

Rather than closing the login form once a user has successfully logged in, hide it by setting its Visible property to False in the form's module. You'll then be able to reference controls in the login form from other objects. In the attached little demo file the user logs in and enters a hashed password. If they then open either of the bound forms their user name and permissions to the form are shown in unbound controls in the form header.

I just used to store static information like that in TempVars() for further use in the app.

 

[DickyP]

Ken's reply makes sense as it is functionally the same as creating a login class (for those with long memories you'll remember using hidden forms as classes in Access 95 before they were formally introduced into Access). I always do this in a class I name 'ThisApp' which contains everything I need to have 'on-tap': often only one or two items but usually a range of them.