By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
446,213 Members | 1,086 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 446,213 IT Pros & Developers. It's quick & easy.

Using VB6 with a MS Access database back-end: configuring access levels

P: 2
Any help would be greatfully recieved here! I'll try and explain the situation here...

I have a database in Access, which is in essence a booking system. I am using VB6 to link to this database. There are people that log onto this system.

The problem / question:

The people that use this database have different access levels. I have some people who I want to have "read-only" access, some people I want to give them "Read / Write" access to, and some people I want to give them "Full Control" access to.

If the level of access these people should have is in the database, and their login details are on this database, how can the access levels be incorporated into VB?

Do I need to create different "classes" of users to this database? I'm not sure where to start.
Feb 27 '07 #1
Share this Question
Share on Google+
3 Replies


100+
P: 1,646
Hi a security table with levels of access is simple enough. assign the levels of security to each login and keep that level of security on a global variable. Test the variable each time they call the db and control the read write capability in vb, not in access. It is not a simple switch on/off thing. You will have to control the entire app in code.

This can be done at the db level using workgroup admin. I am not a fan of that route. I prefer to do it in code
Feb 28 '07 #2

P: 2
Hi a security table with levels of access is simple enough. assign the levels of security to each login and keep that level of security on a global variable. Test the variable each time they call the db and control the read write capability in vb, not in access. It is not a simple switch on/off thing. You will have to control the entire app in code.

This can be done at the db level using workgroup admin. I am not a fan of that route. I prefer to do it in code
Do you mean "do it in code" at the VB end?
Feb 28 '07 #3

100+
P: 1,646
Do you mean "do it in code" at the VB end?
Yessir. That is always my preference.
Feb 28 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.