User-Level Security

[m.cringle]

Please help - I'm in deep poop!

I had an error with one control in my database but to fix needed to
create a whole new MDB file - so I imported everything in to the new
MDB file. The previous database was also split so I imported all the
tables back into this new MDB - I should have ended up with a complete
database with no user-level security in place.

However - when I try to use the User-level security wizard while signed
in as admin user, it tells me that I must be a member of the 'Admins'
user group (a group I already have setup previously). So I sign in as
myself (an admins user) and I'm still told that i must be a member of
the Admins group!

I have also tried logging in as other admins users when opening the new
MDB using my existing security.mdw but with no luck.

Does anybody have any suggestions?

 

[Bill Mosca, MS Access MVP]

Have you tried opening the new database without specifying a workgroup? If
it is truly unsecured, you should be able to get in that way unless your
Admin user has a password in the default System.MDW.

If your FE database was corrupt, why would you need to import the tables in
the BE? BE's rarely corrupt.

 

[m.cringle]

Have you tried opening the new database without specifying a workgroup? If
it is truly unsecured, you should be able to get in that way unless your
Admin user has a password in the default System.MDW.

If your FE database was corrupt, why would you need to import the tables in
the BE? BE's rarely corrupt.

I'm not sure exactly how I did it but I have managed to get access to
my original database again. The exact same problem still exists though
(only admin users are able to use a particular command button which
runs a user-specified query).

The only reason I was importing the tables back into the FE is because
I was unsure how to link the tables again to the BE - I'm guessing I
could have used the table relinking manager?

Unfortunately I'm still stuck with the problem of users other than
(Admininstrators) getting the message 3033: do not have permissions to
access the MSysTables object (or something similar).

Any suggestions? I'm kinda at a loss

I may have mentioned this before (if so please forgive me) but I have

- tried creating a new database by importing everything back in
- created an entirely new workgroup file and user-level security set-up
- Also tried importing original versions of the forms which may be
corrupted

 

[m.cringle]

Have you tried opening the new database without specifying a workgroup? If
it is truly unsecured, you should be able to get in that way unless your
Admin user has a password in the default System.MDW.

If your FE database was corrupt, why would you need to import the tables in
the BE? BE's rarely corrupt.

I'm not sure exactly how I did it but I have managed to get access to
my original database again. The exact same problem still exists though
(only admin users are able to use a particular command button which
runs a user-specified query).

The only reason I was importing the tables back into the FE is because
I was unsure how to link the tables again to the BE - I'm guessing I
could have used the table relinking manager?

Unfortunately I'm still stuck with the problem of users other than
(Admininstrators) getting the message 3033: do not have permissions to
access the MSysTables object (or something similar).

Any suggestions? I'm kinda at a loss

I may have mentioned this before (if so please forgive me) but I have

- tried creating a new database by importing everything back in
- created an entirely new workgroup file and user-level security set-up
- Also tried importing original versions of the forms which may be
corrupted

 

[Joan Wild]

I'm not sure exactly how I did it but I have managed to get access to
my original database again. The exact same problem still exists though
(only admin users are able to use a particular command button which
runs a user-specified query).

Do users have at least read data permissions on this query?

The only reason I was importing the tables back into the FE is because
I was unsure how to link the tables again to the BE - I'm guessing I
could have used the table relinking manager?

Yes, use the Linked table manager. When you import objects, the permissions
you set don't travel with them, so you need to reset them after an import.

Unfortunately I'm still stuck with the problem of users other than
(Admininstrators) getting the message 3033: do not have permissions to
access the MSysTables object (or something similar).

If that is actually the message, then are you modifying the SQL property of
a saved query in code? If so, then users need modify permissions on that
query. See www.jmwild.com/MsysTables.htm

 

[m.cringle]

Hi guys

Thanks for all your help - I really appreciate it

All fixed

I just played around with the user permissions and eventually found a
configuration that worked!