Web Development

Ask something
Discussion Locked

Authentication code utilising logon id

0 helpful
3 replies

by al

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am creating a purchase request system for my company in Access 2000.

On the form, I have created an authentication area. Each request needs three authorisers before a purchase can be made. What I want to do is restrict who can authorise the requests by NT Logon id. I understand that Access has its own access levels as dictated within the JET database, but I would rather do this via Logon ID - then there is no question of a non authoriser, tampering with the security of the database (as canbe done if you know enough about JET) and authorising in the place of the given authoriser.

Is there a neat way in VBA to do this - does anyone have any sample code that could be used for such a purpose?

If I can understand how this works, then we have other databases that could be secured in this way. A colleague has a similar problem.

3 replies

by al

Sorry, this is too complicated - the URL refers to Windows CE too. My DB is access 2000 within Windows NT environment

I was looking for someone who has been through this procedure and may have pointers based on their experiences - sample code or something of that order - if I was good enough to understand MSDN then I would be good enough to understand and solve my problem.

by jrussell

I had a similar problem with an internal application I developed a couple of years ago. I was unsuccessful in finding a way to have MS Access authenticate with an NT Domain user ID so I ended up activating MS Access logons and implemented user level security. I then created an 'Approvers' table with the Access logon ID's and the conditions where each ID could make an approval. Then I had to write some VBA code to get the current Access user, look up the appropriate record in the 'Approvers' table and then make the decision (in code) to allow the user to approve or not. The down side to this was I had to issue user id's/passwords for this database. The upside is that it worked without any problems.

Another option would be to migrate the database to SQL Server, which supports authentication via the NT logon.

This discussion is closed to new replies.