|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
After a day of struggling with it, I finally created a new workgroup with myself as the administrator of a user-level secured DB, with others having limited permissions.
I tested the security by logging onto the DB as one of the limited permission users. All was as expected until...I changed workgroups and joined the default system workgroup (the one that comes with Access installation). Then, the "lesser permission user" had full permissions over the DB.
I presume there is something wrong here, b/c if this was kosher the only way the user-level security is enforced is if the person intentionally joins the workgroup I created. ??????? This is an easy work-around the security if all you have to do is change workgroups.
What did I do wrong?
Thanks, Access Greenhorn
|
|
On Mon, 17 Jul 2006 14:05:01 -0700, Access Greenhorn <AccessGreenhorn[ at ]discussions.microsoft.com> wrote:
[Quoted Text] >After a day of struggling with it, I finally created a new workgroup with >myself as the administrator of a user-level secured DB, with others having >limited permissions. > >I tested the security by logging onto the DB as one of the limited >permission users. All was as expected until...I changed workgroups and >joined the default system workgroup (the one that comes with Access >installation). Then, the "lesser permission user" had full permissions over >the DB. > >I presume there is something wrong here, b/c if this was kosher the only way >the user-level security is enforced is if the person intentionally joins the >workgroup I created. ??????? This is an easy work-around the security if all >you have to do is change workgroups. > >What did I do wrong?
There is something wrong (matter of fact several things)... I would suspect that you didn't create a new, blank db (while logged in with your new workgroup file) and import everything into a new container? Just a guess ... in a properly secured database, users who don't have permissions should receive a "You do not have permissions blah blah" ... Assuming you have a copy of your database, I'd start over again, this time EXACTLY following the guidelines in one of the links below. ULS is tricky and can trip up even experienced developers, so it's best to have a "checklist" of things when you go down this path.
If you don't have a copy (shame on you <g>) then you need to "desecure" your database, check Joan Wild's site for a link titled "Remove security on a database"
Access Security FAQ: http://support.microsoft.com/?id=207793
Here's Lynn Trapp's 10 step plan: http://www.ltcomputerdesigns.com/The10Steps.htm
Joan Wild's site: http://www.jmwild.com/Accesssecurity.htm
Jack MacDonald's site (good read on ULS): http://www.geocities.com/jacksonmacd
> >Thanks, >Access Greenhorn
Scott McDaniel scott[ at ]takemeout_infotrakker.com www.infotrakker.com
|
|
Thanks Scott, the links helped. I followed Joan's steps and it worked out fine. I've been playing around with "junk DBs". I was following about 3 diff textbooks/tutorial textbooks when I did it the first time. I'm still not quite sure what step I hiccupped on.
What is this "container" concept you speak of and that I've come across in other threads? I did not creat a blank DB and import everything into it, if that is what the "container" refers to. My understanding is that you don't have to. After creating a new workgroup, I opened the DB that I wanted to secure and continued on with Joan's steps on how to secure it.
Follow up question:
If I wish to secure another DB or a new DB with this same workgroup I would "join" the security workgroup I created (thru Workgroup Administrator) and start at Joan's step 14?
Thanks for your help, Access Greenhorn
|
|
Access Greenhorn wrote:
[Quoted Text] > I did not creat a blank DB and import > everything into it, if that is what the "container" refers to. My > understanding is that you don't have to. After creating a new > workgroup, I opened the DB that I wanted to secure and continued on > with Joan's steps on how to secure it.
You likely used the security wizard, which creates a new database (container) for you.
> Follow up question: > > If I wish to secure another DB or a new DB with this same workgroup I > would "join" the security workgroup I created (thru Workgroup > Administrator) and start at Joan's step 14?
Yes, 14, 15, and on to 22.
-- Joan Wild Microsoft Access MVP
|
|
Thanks Joan. Could you also help me with another posting of mine, Subject: Inventory on Hand Query? I would greatly appreciate it. It's one of the last design quandaries I need to settle before I really start building this DB, other than in concept and on paper.
|
|
|