Re: Probs accessing database for users of newly developed Superuse

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" wrote:

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 wrote:

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.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-security/200810/1


.

Loading