Failure to compact database

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

ray - 01 Oct 2004 06:29 GMT

When I compacted the database, suddendly came out an error: Record(s) can't
be read; no read permission on 'D:\xxx.mdb'. Can someone advise me the
possible causes and fixes. Access 97 running on Windows XP Pro is used.

Thanks,

Ray

Reply to this Message

Joan Wild - 01 Oct 2004 14:15 GMT

> When I compacted the database, suddendly came out an error: Record(s)
> can't be read; no read permission on 'D:\xxx.mdb'. Can someone
> advise me the possible causes and fixes. Access 97 running on
> Windows XP Pro is used.

The database has been secured, and you are logged in as a user that doesn't
have sufficient permission to compact.

Signature

Joan Wild
Microsoft Access MVP

Reply to this Message

ray - 01 Oct 2004 16:19 GMT

Joan,

How come does the database become suddently secured? No password is used to
open the database at all. I am the owner of the database but not the users.
Your advice is appreciated.

Thanks,

Ray

> > When I compacted the database, suddendly came out an error: Record(s)
> > can't be read; no read permission on 'D:\xxx.mdb'. Can someone
[quoted text clipped - 3 lines]
> The database has been secured, and you are logged in as a user that doesn't
> have sufficient permission to compact.

Reply to this Message

Joan Wild - 01 Oct 2004 18:03 GMT

> Joan,
>
> How come does the database become suddently secured? No password is
> used to open the database at all. I am the owner of the database but
> not the users. Your advice is appreciated.

Access databases do not become secured on their own. Someone must have
secured it (perhaps just by playing in the Tools, Security menu - they may
have run the security wizard on it).

Is there a file in the same folder as the mdb with the same name, but a bak
extension? If so, this is an unsecured backup that the security wizard may
have created at the time it was run.

Signature

Joan Wild
Microsoft Access MVP

Reply to this Message

Ray - 02 Oct 2004 05:05 GMT

Joan,

There is no same name file with bak extension in the same folder. In fact,
only two users are using the databases at the moment and will expend to 4.
The two users are still developing the database by changing the tables,
queries and reports. The new two users are just to read the data.

Based on your suggestion, either one should have right to compact the
database. I will try it next week.

As per current scenario, should I change the database structure to prevent
recurrence. Any recommendation? For example, split database, make mde
database.

Thanks,

Ray

> > Joan,
> >
[quoted text clipped - 9 lines]
> extension? If so, this is an unsecured backup that the security wizard may
> have created at the time it was run.

Reply to this Message

Joan Wild - 02 Oct 2004 14:52 GMT

> Joan,
>
[quoted text clipped - 3 lines]
> changing the tables, queries and reports. The new two users are just
> to read the data.

I take the former 'two users' that are developing have/need full access to
the database. As such, you can't do much to stop them from doing this. It
was likely one of them that played with the security feature. The 'new two
users' are different people, right? These two will make up the 4? If so,
you will at some point want to implement security. Before doing it, be sure
to read up on it via the security FAQ
http://support.microsoft.com/?id=207793

I've also outlined the detailed steps at
www.jmwild.com/AccessSecurity.htm

> Based on your suggestion, either one should have right to compact the
> database. I will try it next week.

If one of them did secure the database (even start the wizard and cancel),
it may be partially secured. Check their computers for any *.mdw files.
There should be only system.mdw found - that is the default workgroup file
that ships with Access and is used in all sessions. If you find more than
that (and you are sure that you have no secure databases), then use the
workgroup administrator (Tools, Security, Workgroup Administrator) to see
which mdw the computer is joined to by default - it should be the system.mdw
you found above.

In addition, if/once they are joined to system.mdw, go to Tools, Security,
Accounts and verify that they have *only* the following:

Two groups - Admins and Users
One user - Admin

Open your database and ensure that the Admin User is the owner of all
objects, and that the Users Group has full permission to every object.

If the Admin User is not the owner of the database, then create a new
database and import all the objects from your database.

> As per current scenario, should I change the database structure to
> prevent recurrence. Any recommendation? For example, split
> database, make mde database.

If the two users need to be developing, then you won't want to make a mde at
this point. Once it is ready to go live with the other two users, you
should distribute a mde (keep the mdb in case further design changes need to
be made).

It is always wise to split the database, and give each user a copy of the
frontend once it's in production.

As for preventing a reoccurrance, about the only thing you can do is to tell
them not to play unless they know what they're doing. Give 'em a swat
upside the head and suggest that they backup before they play.

Signature

Joan Wild
Microsoft Access MVP

Reply to this Message

Ray - 03 Oct 2004 05:53 GMT

Joan,

Thanks for you good advice. I will apply it where suitable.

Ray

> > Joan,
> >
[quoted text clipped - 54 lines]
> them not to play unless they know what they're doing. Give 'em a swat
> upside the head and suggest that they backup before they play.

Reply to this Message

Frank Konzal - 04 Oct 2004 12:24 GMT

You have a #Error in one or more of the memo fields in one of the tables.
The best way to find the problem table is to search memo fields for
something you will not find - I always use 'zzzz'. If the error exists you
will receive an error which states 'you and another user are trying to
change a record at the same time (or something similar). The latest jetutil
will fix it.

> When I compacted the database, suddendly came out an error: Record(s) can't
> be read; no read permission on 'D:\xxx.mdb'. Can someone advise me the
[quoted text clipped - 3 lines]
>
> Ray

Reply to this Message