Compacted and got Conversion Error, now no permissions to fix

[Bonnie A]

Hi everyone. Using A02 on XP. Every few days, I Compact my backend database
file. This morning when it should have finished I got an error. I think
it's the same one I get now but cannot recall. But now if I try to open the
file I get an error saying the DB is in an unexpected state; MS Access can't
open it. It goes on to say it has been CONVERTED from a prior version of MS
Access by using the DAO CompactDB method instead of the Convert DB command on
the Tools menu. This has left the db in a partially converted state. If you
have a copy...use the Convert DB command (I tried and now it says I don't
have nec permissions) etc.

Systems is restoring a copy from last night for me but I wonder if anyone
can give me a clue why this happened so I can avoid it in the future. The
only thing that happened during the compact (I customized my toolbar - adding
the Compact button) this morning was my Lotus Notes calendar reminders that I
snoozed. But they have popped in before.

Thanks in advance for any advice on this issue.

 

[Tom Wickerath]

Hi Bonnie,

Are you compacting over a network? Although lots of people do this, and
never seem to have a problem, I strongly advise that one first copies the BE
database to their local hard drive, before attempting a compact and repair.
Access is very suseptible to corruption due to bad writes, which can happen
if you have any type of network noise.

After you get a restored version of your database, I suggest copying it to
your local hard drive. Rename it with perhaps "_old" in the filename (ie.
MyData.mdb becomes MyData_old.mdb). Create a brand new database in Access.
Use the "_old" version as a source for the new database. I give complete
instructions on the bottom of page 3 of a Word document that I call Access
Links.doc. You are welcome to download a zipped copy from my web site:

http://www.accessmvp.com/TWickerath/

Then use your new database in place of the restored copy.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________

 

[Bonnie A]

Hi Tom,

I have long told our systems folks that when the network burps Access feels
it. Fortunately, our files are backed up each night and I got a new copy
pretty quickly. I think I'll start compacting in C though in the future.

Thank you VERY much for your time and information. I'll check out your
article as well.

 

[Tom Wickerath]

Hi Bonnie,

I have long told our systems folks that when the network burps Access feels
it.

This is the reason I include code to automatically close the database, due
to inactivity, after a set period of time (generally 15 minutes). Access is
most suseptible to corruption due to interrupted write operations, so I don't
want a person to be in the middle of editing a record, get busy with some
other task, and then leave Access in this state for a long period of time.
You can see the technique I use in my Multiuser Applications paper, under the
subtitle "Close inactive sessions":

Implementing a Successful Multiuser Access/JET Application
http://www.accessmvp.com/TWickerath/articles/multiuser.htm


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/expert_contributors.html
__________________________________________