Re: Probs accessing database for users of newly developed Superuse

Tech-Archive recommends: Speed Up your PC by fixing your registry

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

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?

--
Joan Wild
Microsoft Access MVP
"CB" <CB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EB773C6C-D244-486B-9F2A-CF27DE9CE468@xxxxxxxxxxxxxxxx
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



.

Relevant Pages

  • Re: List Users Permissions down to table.column action
    ... THIS STORED PROCEDURE GENERATES COMMANDS ... -- FIXED PROBLEMS WITH STATEMENT LEVEL PERMISSIONS GRANTING. ... -- CREATE TABLE TO HOLD LIST OF USERS IN CURRENT DATABASE ... -- GRANT USER ACCESS TO SERVER ROLES ...
    (microsoft.public.sqlserver.security)
  • Re: User access on a company intranet
    ... Yes they need full permissions on the folder where the backend is. ... You wouldn't need to do this in your copy of the database. ... However you can toggle the shiftkey bypass from another mdb file. ... When you want to implement security, you create a new mdw file, ...
    (microsoft.public.access.security)
  • Re: Active directory corruption
    ... During an installation of PHP I accidentally changed permissions for the ... Active Directory database is unavailable because it is damaged, ... Open a command prompt and run NTDSUTIL to verify the paths for the ...
    (microsoft.public.windows.server.sbs)
  • Re: Active directory corruption
    ... default web site and copied the permissions to all the child ... as it may not be the database that is the problem. ... prompt, use the ESENTUTL to check the integrity of the database. ... To recover the database type the following at the command prompt: ...
    (microsoft.public.windows.server.sbs)
  • Problem is w/ .ADP..Re: SQL db Permissions for users not working
    ... You do not have SELECT permissions on the ... SysObjects system table in the database. ... figured out that qualifying the database owner (dbo in my ... >> I feel that the object owner is not dbo, ...
    (microsoft.public.sqlserver.security)