Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Compact database error message 1

Status
Not open for further replies.

Cads

Technical User
Jan 17, 2000
40
GB
We have an Access 97 database here at work which I've developed and now administer. It's been in use for ~18 months by 6-8 people. Each month, because of data imports from another system, I compact it in the usual way through Database Utilities and, up until now, no probs. As usual I make sure no-one else has access to it. However......

On trying to compact today, I'm getting an error message "Records cannot be read, no read permissions on G:\..." which follows with the database path and name.

I thought my prayers had been answered in the Microsoft Knowledgebase article Q301869 but both reasons given there don't seem to apply. Any further thoughts/ideas/solutions please?
 
From your use of the drive notation G:\ I'm guessing the db is on a networked share/project drive. Is the share full? Or at least so full that there isn't space for Access to create a copy of the database called db1.mdb (the first thing that happens during compaction).

I know the text of your error message doesn't seem to point to this, but I seem to recall getting similar error messages under A97 when I encountered this file space problem. [pc2]
 
Unfortunately that's not the case. Database is 34Mb. Available disk space 9.26Gb. Thanks for replying.
 
Oddly enough you can have too much space for some applications which were designed at a time when 2 Gb was the max. eg SQL Server 6.5 can even see negative free space.

So it may still be worth copying to a local drive and compacting there. If nothing else it just eliminates that possibility.

Ken
 
I'm pretty sure this is a corruption issue.

1. If the .LDB file is still there, delete it.
2. Try to compact through the user interface.
3. If that fails, use JetComp.exe instead.
Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@yahoo.com
 
Thanks for suggesting the problem might lie with database corruption. I used the Repair Database facility and then compacted, and it was fine.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top