Access Permissions not set

[OllyH]

I recieve a large number of mdb files from a coleague which do not have any
permissions set for any usergroups or users. When I go to Tools > Security >
User and Group Permissions none of the boxes are ticked for any user/table.
Also in the Change Owner Tab all the tables have their current owner set to
unknown. This causes my systems to fail.

Is there a reason why my coleagues Access does not set these permissions by
default (as everyone elses' does) and how can I fix it? both My coleague and
myself are using Access 2003.

Thanks for any help!

 

[Arvin Meyer MVP]

You have to be more specific. How does your system fail? What are the error
messages and error numbers?

 

[Tom van Stiphout]

On Wed, 1 Jul 2009 02:58:01 -0700, OllyH

What do you mean with "causes my systems to fail"? An exact error
message would be nice, as well as when exactly this error occurs.

-Tom.
Microsoft Access MVP

 

[OllyH]

the message is:

Microsoft JET Database Engine error '80040e09'

Record(s) cannot be read; no read permission on 'pl011401METADATA'


pl011401METADATA is a table within an access database.

The system fails because the permissions are not set. I need to know how to
get my colleagues access to set the permissions as the defult permissions
which are usually used in access. Or I need to know why they are not being
set as default.

 

[John W. Vinson]

I recieve a large number of mdb files from a coleague which do not have any
permissions set for any usergroups or users. When I go to Tools > Security >
User and Group Permissions none of the boxes are ticked for any user/table.
Also in the Change Owner Tab all the tables have their current owner set to
unknown. This causes my systems to fail.

Is there a reason why my coleagues Access does not set these permissions by
default (as everyone elses' does) and how can I fix it? both My coleague and
myself are using Access 2003.

Thanks for any help!

The problem would appear to be that you're joined to a workgroup file that
removes permissions from the default ADMIN user. This is appropriate for a
secured database.

If your colleague didn't apply security to the database, then the Admin user
should have full rights to everything. You just need to use Tools...
Security... Workgroup Administrator to Join an unmodified, default copy of
SYSTEM.MDW. This will give you an Admin user ID and your colleague's databases
should work.

 

[David W. Fenton]

the message is:

Microsoft JET Database Engine error '80040e09'

Record(s) cannot be read; no read permission on 'pl011401METADATA'

pl011401METADATA is a table within an access database.

That's not a Jet error number.

 

[Arvin Meyer MVP]

If you can open the database, but not do anything, the database has a
different workgroup which you must join. That will have a different .mdw
file, normally located in C:\Windows\System32\ folder, but it can be
anywhere. You may, or may not, be prompted for a username and password. You
could also be missing permissions on the folder where the databases are
stored.