Probs accessing database for users of newly developed Superuser gr

[CB]

Hi everyone,

I have a split database (Access 2003) that employs USL. Users access the
database from a shortcut on their desktop. I have been having problems when
logged in as a Full-data user that I have not been able to resolve (see
posting here: http://tinyurl.com/3ljnx3). As a result, I decided to use the
Security feature (Tools/Security…) to create a new group called Superuser.
This group is to have virtually all permissions except administer. I then
assigned two users to the group.

When I try to log in as one of those two users (using the same shortcut I
used to change the permissions!), I get the error message “You do not have
necessary permissions to use <….> object. Have your system administrator or
the person who created the object establish appropriate permissions for you.â€

What gives???? I’m really pulling my hair out between this issue and my
previous issues (shown in the above link). I really do not want to add these
two users to the Admins group but I might have to so I can deploy this
database to another city (which I need to do fairly soon).

Thanks for any and all help!

Chris

 

[CB]

Oops. The url for previous problem is http://tinyurl.com/3ljnx3

 

[Chris O'C via AccessMonster.com]

Give this new group database open/run permission.

Chris
Microsoft MVP

 

[CB]

Hi Chris,

Thanks for the prompt supply. This group had open/run, open exclusive, and
administer privileges on the database. I tried changing it to just open/ run
- no difference. I changed in back to full permissions - still no luck.

Chris

 

[Chris O'C via AccessMonster.com]

Are you positive you've given the open/run permission on the same db file the
superusers are opening? Are you positive you're both using the same
workgroup file when opening the db? Go to the immediate window and paste
this and push the enter key:

? syscmd(acSysCmdGetWorkgroupFile)

Next, paste this and push the enter key:

? currentdb.Name

Do they match the paths and file names in the superusers' shortcut's target?

Chris
Microsoft MVP

 

[CB]

Yup, I’m positive. Perhaps I should clarify a little further what I’ve done….

Using the shortcut on my desktop, I logged in as administrator and held-down
the shift key so I had full menu access (I’ve disabled virtually everything
in Tools/Startup). This was how I created the new Superuser group and added
the two users. I then exited the program.

Using the *same* shortcut, I logged in using the name of one of the two
users I added to Superuser. This is when I received the error message.

In following your instructions, I used the shortcut to log in as
administrator (holding down the shift key so I had access to the Code button)
and noted the WIF and database. I then exited.

Here’s where it gets weird!!!!

When I tried to log in as one of the Superusers, I held down the shift-key
(otherwise I wouldn’t have access to the Code button). I was able to enter
the database!!! The instructions in the Immediate window confirmed I was
using the proper WIF and database. When I closed the VB window, I noticed
that my switchboard was open in design view. When I tried to switch back to
form view, I got the error “You do not have the necessary permissions …..â€
When I selected OK, the dialogue box closed but I was still in the database -
just couldn't switch the view of the switchboard

Now I’m really confused.

Chris

 

[Chris O'C via AccessMonster.com]

Push down on the shift key and use the shortcut to open the secure db as one
of the superusers. Open the user and group permissions window and check that
this user is listed as a member of the superuser group.

Chris
Microsoft MVP

 

[Chris O'C via AccessMonster.com]

Sorry, my bad. I meant open the user and group accounts window to verify the
list of groups this user is a member of.

Chris
Microsoft MVP

Push down on the shift key and use the shortcut to open the secure db as one
of the superusers. Open the user and group permissions window and check that
this user is listed as a member of the superuser group.

Chris
Microsoft MVP

Yup, I’m positive. Perhaps I should clarify a little further what I’ve done….

[quoted text clipped - 24 lines]

Chris

 

[CB]

Good morning Chris,

I logged in as one of the users in Superuser and checked the accounts
window. Both users are listed as members of Superuser. Interestingly enough,
I accidently selected the User and Group Permissions window and when I tried
to select a group a dialogue popped up stating:

"You can't view this object's permissions. To view or change permissions for
this object, you must Administer permission for it. For more information on
permissions and who can set them, click Help."

Chris

Sorry, my bad. I meant open the user and group accounts window to verify the
list of groups this user is a member of.

Chris
Microsoft MVP

Push down on the shift key and use the shortcut to open the secure db as one
of the superusers. Open the user and group permissions window and check that
this user is listed as a member of the superuser group.

Chris
Microsoft MVP

Yup, I’m positive. Perhaps I should clarify a little further what I’ve done….

[quoted text clipped - 24 lines]

Chris

 

[Chris O'C via AccessMonster.com]

That message is normal for users who don't have administer permissions.

Since the superuser can get in by pushing the shift key when opening the db,
are you sure you don't have vba code or a macro running on startup preventing
certain users from opening the db?

Chris
Microsoft MVP

 

[CB]

Hi Chris,

Yes, I'm sure. I created the database several years ago and am modifying it
for my current company. I have only a little experience with writing code so
I wouldn't have come up with something that elaborate on my own. I have
received help with code from others but nothing to do with preventing certain
users from opening the db.

The only macros I have are for exiting the program, getting the user name,
launching Excel spreadsheets, and having Outlook send me an e-mail when the
user clicks a button. I took a look at the various pieces of code and I can't
see anything that might prevent certain users from opening the db.

Might something be corrupt?

Regards,
Chris

 

[Chris O'C via AccessMonster.com]

If security features are corrupt, nobody gets in or they're corrupt for
everybody on the same objects, but mostly nobody gets in.

I'm out of ideas, maybe somebody else has some more.

Chris
Microsoft MVP

 

[CB]

Well, thanks for efforts, Chris. I appreciate your patience!

Chris

 

[Joan Wild]

I'm working offline, so can't go to your link, but what does the message
say? i.e. what is in the <...> part - the database, a table/query/form?

 

[CB]

Hi Joan,

Thanks for responding!

The <...> contains the path to the database file, i.e., they don't have
permissions to open the database. Its the same message that would appear if a
user tried to open the secured database by double-clicking on the file name.

FWIW, I've asked Chris in another post if it might have something to do with
the fact that my WIF was created in Access 2000 but I've since updated my
database to A20002-2003. What are your thoughts on that?

Regards,
Chris

 

[Joan Wild]

Shouldn't matter. You need to verify the permissions on the Database
object - sounds like they aren't what you think they are, or users are
looking at a different version of the FE. Permissions are stored in the mdb
file, not the mdw.

 

[CB]

Hi Joan,

I've checked permissions countless times. I've gone so far as to give the
Superuses group full administrative permissions on every single object
including the database - identical settings as the admins group (only as a
test). My Superusers STILL aren't able to log in.

Actually, my Superusers aren't using the database yet. I log in as
administrator and change what I need to change then I log out. I then try to
log in as one of the Superusers and thats when I have problems.

The weird this is that when I log in in as a Superuser AND hold down the
shift key I can at least enter the database. I can't open tables in any view
but can create new ones. The queries won't run or open in design view but
they will open in SQL view. Forms won't open in form view but will open in
design view. In this case, each text/comb box has an error (?) and when I
select the '!' I see "Invalid control property: control source" and "No such
field in the list." If I try to make a new form, I can select a table but
there are no fields available. Reports will open in design view but the
controls have the same error as the ones on the forms. Macros run fine.

Chris

 

[Joan Wild]

Holding down the shiftkey does not bypass any security permissions, so if
that succeeds, then you don't have a permissions problem with the database
object.

So something in your startup is causing this - from your other post, I'd say
it has to do with the Switchboard and Switchboard Items (I assume you have
startup set to open the Switchboard form on opening).

Check the code behind your opening form, or in an autoexec macro.

What exactly are you doing on starup?

 

[CB]

Hi Joan,

Sorry for the delay in getting back to you. I wasn't in the office after the
long weekend.

Yes, Startup is set to open the Switchboard form on opening. None of the
options in the Startup dialogue are checked and the menu bar and short cut
menu bar are set to default. I do not have an autoexec macro that runs at
startup.

I think I used the Switchboard manager to create the Switchboard. I say "I
think" because I created the original database about eight years ago and was
away from it for five years. I'm not familiar enough with code to have
written the switchboard's code from scratch; hence, I must have used the
manager. I've included the code for when the form opens below. Its seems
pretty straight forward.

Private Sub Form_Open(Cancel As Integer)
' Minimize the database window and initialize the form.

' Move to the switchboard page that is marked as the default.
Me.Filter = "[ItemNumber] = 0 AND [Argument] = 'Default' "
Me.FilterOn = True

End Sub

Because the startup is prettty straightforward, I would have that if there
was a switchboard problem that problem would exist for all groups. Instead, I
see different problems for users of different groups.

Thanks for your assistance! I really appreciate it.

Chris

 

[Joan Wild]

I'm sorry, but I've lost track of your problem here.

You have secured your mdb, but the SuperUsers cannot get into it. You've
double-checked their permissions and all are correct. If they hold down the
shiftkey while opening, then can get in.

Makes no sense to me.

--
Joan Wild
Microsoft Access MVP

Hi Joan,

Sorry for the delay in getting back to you. I wasn't in the office after
the
long weekend.

Yes, Startup is set to open the Switchboard form on opening. None of the
options in the Startup dialogue are checked and the menu bar and short cut
menu bar are set to default. I do not have an autoexec macro that runs at
startup.

I think I used the Switchboard manager to create the Switchboard. I say "I
think" because I created the original database about eight years ago and
was
away from it for five years. I'm not familiar enough with code to have
written the switchboard's code from scratch; hence, I must have used the
manager. I've included the code for when the form opens below. Its seems
pretty straight forward.

Private Sub Form_Open(Cancel As Integer)
' Minimize the database window and initialize the form.

' Move to the switchboard page that is marked as the default.
Me.Filter = "[ItemNumber] = 0 AND [Argument] = 'Default' "
Me.FilterOn = True

End Sub

Because the startup is prettty straightforward, I would have that if there
was a switchboard problem that problem would exist for all groups.
Instead, I
see different problems for users of different groups.

Thanks for your assistance! I really appreciate it.

Chris

Holding down the shiftkey does not bypass any security permissions, so if
that succeeds, then you don't have a permissions problem with the
database
object.

So something in your startup is causing this - from your other post, I'd
say
it has to do with the Switchboard and Switchboard Items (I assume you
have
startup set to open the Switchboard form on opening).

Check the code behind your opening form, or in an autoexec macro.

What exactly are you doing on starup?