Why does system crash when Compact and Repair Database is used?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In Access 2003 the command 'Compact and Repair Database' causes the system
(Windows XP Professional) to crash, with an error message saying it has to
close.
Why is this and what do I have to do to stop it?
 
Does it happen on every machine? or just 1 machine? What other software is
running? Does this machine have older hardware? Has the operating system
been upgraded? or is it the original system that was first loaded on the
machine? Is the machine on the network? What permissions do the users have?

The answers to these questions may lead us to a solution.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 
I sometimes come across the problem where compacting and repairing a database
will actually corrupt my database, or invalidate the links to my tables.
Mostly I think this is due to the complexity of the front-end I am working
on, or the number of different databases I'm linked to, or just whatever else.

Anyway, make sure you're making a backup copy of your database before you
try to compact and repair. You said yours is crashing when you try doing
that, so test it on a simple database to see if it'll work on something
small. If that doesn't work, try converting to an older version of Access
first (Acces 2000 or in an extreme circumstance, Access 97). Failing that,
try compacting on a different machine. If it's still crashing, then it's
probably an Access problem, and you'll want to re-install Office on your
machine. If it's not working by that point, I would personally re-install
the OS (because it might be a library or extension problem), but that's just
me. I'm odd like that. :-p

hth,

Nick
 
It's a 3-month old single machine (Dell)
The hardware is unaltered
The operating system is original and updated only by MS automatic updates
The application software (MS Office 2003 Pro) is as pre-installed.
No network connection / single-user with full rights
McAfee Security Center is running, with rights granted to MS Access
Thanks for your response,
R J Kershaw
 
Thanks for your reply.
I have already done the backup bit (sound advice anyway), but there is no
apparent corruption and the links are still there.
Will try the procedure with a completely unlinked DB.
Unfortunately there is no other machine to test this on so I hope it doesn't
come to the need for application or operating s/w reinstallation - I have too
much else going on!
Best regards,
Bob K
 
Temporarily disable your McAfee; disconnect from the Internet if you want to
feel safe if you have a 'always on' connection. McAfee can interfere with
Microsoft from time to time.
Also make sure the location of the database has enough hard drive space,
which I tend to believe that is okay, since your machine is new.

The other option you have is create a new database and import tables first,
then queries, then compact that part. Continue importing the remainder of
your database. Do forms last, as sometimes a form gets corrupted and it
prevents the import of other items. If you do have a corrupted form, then
you may have to just recreate that form in the new database. Once everything
is imported, make a backup copy and then compact that new database.
 
I know this one ... but there is no answer. It's a bug.

I'm going to bet it only happens after you've had a code window open.
Try this: before attempting to compact, close all code windows and
save. (Windows | Close All Windows and File | Save)

Now close the Visual basic IDE and compact. In my experience, the
problem with error on Compact goes away.

I have observed this and a good friend who is an Access guru has
reproduced it. It's a bug.
 
There has been a few posts that suggest that having code windows open can
case this..

Try he following:

exit the application

re-enter the application (hold down the shift key if you have any startup
forms..or any startup code that runs when the application loads).

now try a compact and repair. If this don't work..then I would suggest that
you create a new blank database..and import everything into this...can you
compact that one?

It sounds like you have a improper shutdown or free up..and the mdb files is
now damanged....

Also, what format of mdb file are you using...(the default is 2000...but
give the 2002-2003 format a try).
 
I'll suggest 3 things:

1. If this started to happen after an automatic update, roll back to the
machine state before the update.
2. Shut down McAfee (disconnect from the Internet before you do). Change
your AV if this works. I use AVG without any problems with Access.
3. Close all objects and code windows before attempting a compact.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
 
Many thanks for your kind assistance.
Bob K

Arvin Meyer said:
I'll suggest 3 things:

1. If this started to happen after an automatic update, roll back to the
machine state before the update.
2. Shut down McAfee (disconnect from the Internet before you do). Change
your AV if this works. I use AVG without any problems with Access.
3. Close all objects and code windows before attempting a compact.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access
Click to expand...
 
Many thanks for your kind assistance.
Bob K

G. Vaught said:
Temporarily disable your McAfee; disconnect from the Internet if you want to
feel safe if you have a 'always on' connection. McAfee can interfere with
Microsoft from time to time.
Also make sure the location of the database has enough hard drive space,
which I tend to believe that is okay, since your machine is new.

The other option you have is create a new database and import tables first,
then queries, then compact that part. Continue importing the remainder of
your database. Do forms last, as sometimes a form gets corrupted and it
prevents the import of other items. If you do have a corrupted form, then
you may have to just recreate that form in the new database. Once everything
is imported, make a backup copy and then compact that new database.
Click to expand...
 
Many thanks for your kind assistance.
Bob K
p.s. this never happened in years with Access97 & Windows98!
 
Thanks for that, Albert.
I now have a number of things to try along similar themes.
One observation: there is apparently no corruption or data loss taking place
and the filesize indicates that at least some compaction is happening.
The mdb type is 2003, the default for Access2003.
Best regards,
Bob K
 
This is ABSOLUTELY a bug in Access 2003. It not only happens
consistently when you have had a module window opened, but if you have
designed ANY object.

I have a fairly sophisticated front end application that I have
attempted to bring into a new database to try to eleviate the problem,
but it still happens.

The only thing that you can do is make your changes, then fully exit
the application, then you can come back in and Compact.

I wish that Microsoft would just own up to this and fix it. This never
happened in 2000 or 97.

Also, the application seems to crash alot more now that we have
converted it to Access 2003. Again - it was pretty stable in Access
2000, but our IT Dept. forced us to upgrade, so we did. We have had
more problems between the stupid Outlook security (which - we were
finally able to overcome) and these constant crashes.

I think that I've definitely learned my lesson on "if it ain't broke -
don't fix it" and will fight harder next time against an upgrade until
I see the tru benefits.

Good Luck!
 
This is ABSOLUTELY a bug in Access 2003. It not only happens
consistently when you have had a module window opened, but if you have
designed ANY object.

I have a fairly sophisticated front end application that I have
attempted to bring into a new database to try to eleviate the problem,
but it still happens.

The only thing that you can do is make your changes, then fully exit
the application, then you can come back in and Compact.

I wish that Microsoft would just own up to this and fix it. This never
happened in 2000 or 97.

Also, the application seems to crash alot more now that we have
converted it to Access 2003. Again - it was pretty stable in Access
2000, but our IT Dept. forced us to upgrade, so we did. We have had
more problems between the stupid Outlook security (which - we were
finally able to overcome) and these constant crashes.

I think that I've definitely learned my lesson on "if it ain't broke -
don't fix it" and will fight harder next time against an upgrade until
I see the tru benefits.

Good Luck!
 
I get this problem when I have a digital certificate and a library MDE, which
also has a digital certificate. Remove the digital certificates and the
Repair Compact works. Have same problem with Backup Database.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Split database crash 2
Compact and Repair a Database 2
Compact and Repair Advice 14
compact and repair when database is split 10
Compacting an Access database 3
Compact and Repair Database? 4
Compact and repair 1
Compact & Repair Question 1

Back
Top