D
D
To anyone who can assist,
I'm still relatively new to access and I'm trying to wrap my mind around
implementing an application role. The idea behind this is that I'm hoping to
avoid having to create 1000's of user logins for access (select, update,
delete) to just 2 tables in my db. Needless to say, my search in finding
answers on the "how" peice isn't getting me very far. I found a website and
attempted even using the Northwind db test and it still didn't seem to work
(http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q308312). From what
I've read so far, using app roles in adp is quite the challenge. For what
I'm trying to accomplish, does this sound like something worth undertaking
and if so any leads on how I can get there?
I'm still relatively new to access and I'm trying to wrap my mind around
implementing an application role. The idea behind this is that I'm hoping to
avoid having to create 1000's of user logins for access (select, update,
delete) to just 2 tables in my db. Needless to say, my search in finding
answers on the "how" peice isn't getting me very far. I found a website and
attempted even using the Northwind db test and it still didn't seem to work
(http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q308312). From what
I've read so far, using app roles in adp is quite the challenge. For what
I'm trying to accomplish, does this sound like something worth undertaking
and if so any leads on how I can get there?