maximyshka
asked on
User authentication with MS ACCESS 2007
Hi,
I need to implement user authentication in ms access 2007 application. I need to create user roles and permissions to wirte some records , but not only to read from other records. Also, I would like to track which user modified record.
I have a multi user ms access application with back end on SQL server 2008, but i need to implement security on ms access not in sql server. Any suggestions or may be vba code samples?
I need to implement user authentication in ms access 2007 application. I need to create user roles and permissions to wirte some records , but not only to read from other records. Also, I would like to track which user modified record.
I have a multi user ms access application with back end on SQL server 2008, but i need to implement security on ms access not in sql server. Any suggestions or may be vba code samples?
Agree with peter: Why would you go to this trouble when you have a robust security system in place with SQL Server?
I can certainly understand wishing to build a navigation system in 07 (where UserA can open FormB but not FormC, for example). If that's the case, then you might check out LASsie by Peter's Software (www.peterssoftware.com), which shows how to do this.
You can also build this yourself by adding tables to track Users, Groups, User + Group Associations and Object + Group permissions. It's not overly complex, but will take some work to implement. Once you've defined the permissions, then just build a group of VBA functions that provide you an easy interface to determine permissions, and you should be okay.
I can certainly understand wishing to build a navigation system in 07 (where UserA can open FormB but not FormC, for example). If that's the case, then you might check out LASsie by Peter's Software (www.peterssoftware.com), which shows how to do this.
You can also build this yourself by adding tables to track Users, Groups, User + Group Associations and Object + Group permissions. It's not overly complex, but will take some work to implement. Once you've defined the permissions, then just build a group of VBA functions that provide you an easy interface to determine permissions, and you should be okay.
ASKER
i plan to use accdb (access 2007). I need to provide user based functions on ms access forms.
Access forms provide several different methods to allow/disallow basic user interaction with your data:
AllowEdits
AllowDeletions
AllowAdditions
As well as the standard .Enabled and .Locked properties of controls and such. So you could do as i suggest, and build your tables to house your various items, and then build functions to interact with those tables to determine which user can interact with which object.
If you build the tables and post them back here, we can critique them and let you know what changes need to be made.
AllowEdits
AllowDeletions
AllowAdditions
As well as the standard .Enabled and .Locked properties of controls and such. So you could do as i suggest, and build your tables to house your various items, and then build functions to interact with those tables to determine which user can interact with which object.
If you build the tables and post them back here, we can critique them and let you know what changes need to be made.
ASKER
so i create table users, whic will contain userName, Password, permision level
Once user loged in , i can check user password and permision level and open form . How can i track loged in user through application, through other forms?
Once user loged in , i can check user password and permision level and open form . How can i track loged in user through application, through other forms?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I guess I can create module with global variable Global GBL_Username As String , and record username . then when i open each form i will have to run this variable against permission level .
ASKER
why do you think that global variable a bad idea?
Having asked that, if your backend is a secured sql server database I cannot understand what you feel you can gain by securing the front-end?