Re: You don't have permission to read

OK, then you are opening the secured database using a secure workgroup. In
a secured mdb, generally the Admin user does not have permission to do
anything.

You should log in using a username that does have permissions.

That said, the fact that the owner shows as unknown, indicates that you are
not using the workgroup file that was used to secure it with. You need to
find that workgroup file, if logging in as another user doesn't do it.
There has to be at least one user that is a member of the Admins Group - can
you log in as that user?


--
Joan Wild
Microsoft Access MVP

Len wrote:
> I am using a desktop shortcut as follows:
>
> "C:\Program Files\Microsoft Office\Office10\MSACCESS.EXE"
> "s:\external\external.mdb" /wrkgrp "s:\external\soni.mdw"
>
> There are no problems in running the system using either Admin or
> another user login that was set up. The problem is changing objects.
> I cannot change any objects - get the message "You don't have
> permission to read - object name". I then checked the owners of the
> database itself and the objects - showed <unknown>. Tried to
> specifically change the permissions of an object and again got a
> similar message - don't have permission to read. Also compacted and
> repaired with no problem thinking that might fix problem.
>
> Thanks - Len
>
> "Joan Wild" wrote:
>
>> When you say 'using Admin as my login', are you referring to an
>> Access username, or a Windows username. In other words, do you get a
>> username/password prompt while opening the mdb?
>>
>> --
>> Joan Wild
>> Microsoft Access MVP
>>
>> Len wrote:
>>> I have been asked to modify a database that has not been touched for
>>> over a year. Using Admin as my login I get the above message. I get
>>> the same error message when trying to open any object. The owner of
>>> the database and each of the objects is shown as <unknown>. I have
>>> also tried to export objects but again get the same error message.
>>> Any suggestions. Thanks - Len


.

Relevant Pages

  • Re: New Problem that I need help with
    ... administrator section to see what workgroup they belonged to. ... and the Users Group and the Admin User are ... You could join the secure mdw as your default, ... That is not likely the secure mdw you created when you secured the ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)
  • Re: Workgroup files and Open/Run in 2002
    ... The DEFAULT workgroup isn't going to have the Admin user removed from the ... The secured workgroup file does. ... permissions from the Users group along with modifying the permissions while ... >>> joined to the standard system.mdw, then your database isn't secure. ...
    (microsoft.public.access.security)
  • Re: New Problem that I need help with
    ... The db on my backend is a mdw. ... Tools, security, workgroup administrator. ... secure mdw on the server. ... Group and the Admin User are common to all. ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... The first step is to create a new workgroup. ... > I created the Administrator and added him to the admin ... > No luck if I try to open the database from a computer that> is attached to the default workgroup I have full access to> the entire database. ... >>Should secure your database enough. ...
    (microsoft.public.access.security)