Access 2002 DB keeps asking to be repaired

  • Thread starter Thread starter Travis C.
  • Start date Start date
T

Travis C.

I have a database that's been working fine for 3 years or
so. OS is Win2k pro, sp4, with Office XP sp3, Access
version 2002, sp3. For the past week, everytime I open the
DB, it says it needs to be repaired. The repair seems to
work ok but it asks again almost daily. Has anyone run
into this behavior? If so, did you find a cure?

Thanks in advance,

Travis
 
Travis C. said:
I have a database that's been working fine for 3 years or
so. OS is Win2k pro, sp4, with Office XP sp3, Access
version 2002, sp3. For the past week, everytime I open the
DB, it says it needs to be repaired. The repair seems to
work ok but it asks again almost daily. Has anyone run
into this behavior? If so, did you find a cure?
Click to expand...

The obvious question is what changed a week ago? A new system? A new
server? Patches to server? Flaky power? Someone's laptop going into
hibernation after inactivity? (Usually senior mg mt. <smile>)

For more information on corruption including possible causes,
determining the offending PC, retrieving your data, links, official MS
KB articles and a list of vendors who state they can fix corruption
see the Microsoft Access Corruption FAQ at
http://www.granite.ab.ca/access/corruptmdbs.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
I have a database that's been working fine for 3 years or
so. OS is Win2k pro, sp4, with Office XP sp3, Access
version 2002, sp3. For the past week, everytime I open the
DB, it says it needs to be repaired. The repair seems to
work ok but it asks again almost daily. Has anyone run
into this behavior? If so, did you find a cure?

Thanks in advance,

Travis
Click to expand...

Check out the suggestions at

http://www.granite.ab.ca/access/corruptmdbs.htm

You may want to start by creating a new, empty database and importing
everything. The first things to check are if there is a bad NIC on
some computer in the network, or a user who's turning off or rebooting
while Access is open.
 
Back
Top