Database compacting problems

[DeborahP]

Hello,

I am in need of some help!

I have a large database that is shared among 250 users. The server the database resides on is having some problems and has caused me many headaches.

I was able to run the repair and it corrected the table problems, however, I can not compact it. The error message below is what I am getting.

"Record(s) can't be read; no read permission on m:\calendar\Calendar.mdb"

I tried to export all the tables and I get an error message stating that I don't have read permissions. I have made sure all the permission are correct.

Can the .mdw file get corrupted? What do I do if this is the problem?

It is secured and I am the admins user. Please help! I need to get it back online very soon!

Thanks,
Deborah

 

[The_Doc_Man]

That's not an Access error; it is a Windows error.

You need the server administrator to look at the file to see if its permissions have gotten mangled.

In general, in a Windows environment, you need the following permissions for using Access databases...

(Summary permissions): On all files - read, write, modify, delete
On the folder: read, write, modify

More specifically, you need file create/delete/read/write/modify rights in the folder 'cause you need those to manage the .LDB file.

You need file read/write/modify on the .MDB file

If you have the ability to import or export data inside the shared folder, you will also need read/write/modify/create/delete for those operations.

If you need the detailed permissions, I can look them up for you. But the ones I named should be enough for your server admin.

BTW, to make him feel better about it, if the folder holding the DB is a top-level folder (appears in the drive's root), that maximizes privacy issues. If the folder is NOT a top-level folder, you will also need read permissions on all members of the path leading to that folder. Or I think the detailed permission in that case is TraverseFolder

 

[WayneRyan]

Deborah,

Are you sure that you have full rights (Windows rights) to the directory(s)
involved?

If so, try creating a new blank database. Then individually import your
items into it. At first you might "select all", but if you encounter
errors, you'll have to become selective. There is probably some object
in your db that is corrupt.

Sometimes when this happens, Access will leave a "db1.mdb" file. In
some instances this database has all of your valid objects in it. Look
at the contents of this DB, it might give you some hints. If you have
failed repeatedly, you might find db1, db2, db3, ...

This is just one of those things that Access does at times ...

Wayne

 

[Oy Vey]

1. Copy the .mdb to your desktop or another folder where you have full permissions.
2. Attempt to compact.
3. When that fails, go to each table and attempt to sort. When you get that error again, you'll have found your corrupted table/record.

If you are lucky, you should be able to find the corrupt record and delete it. If not, you will need to dump the table to a text file, recreate the table after deleting the existing one and reimport the data.

Also, if you're using memo fields, see if there is any way you can avoid their use. Memo fields + network users = frequent corruption.

 

[dan-cat]

250 users + 1 mdb file =

Time for your boss to cough up on SQL server

 

[PookaTech]

Thanks

Hey, Thanks to everyone for posting back to this thread. A quick search and this was the first thread that showed up and is definitely going to save my A$$ tomorrow. These forums rock because of the people on them!

Pookatech