Corrupt database

  • Thread starter Thread starter Neil Jordan
  • Start date Start date
N

Neil Jordan

Our organisation database keeps falling over. I have
found that spurious data in the form of small boxes keeps
appearing in Date/Time fields. When I try to access the
table and the record with the corrupt data, the database
shuts down. I have in the past been able to compact and
repair the database but its having none of it this time.
Any ideas as to why I am getting the small symbols in the
date/time fields and any ideas on recovery?

Neil J
 
Our organisation database keeps falling over. I have
found that spurious data in the form of small boxes keeps
appearing in Date/Time fields. When I try to access the
table and the record with the corrupt data, the database
shuts down. I have in the past been able to compact and
repair the database but its having none of it this time.
Any ideas as to why I am getting the small symbols in the
date/time fields and any ideas on recovery?
Click to expand...

Check out Tony Toews' excellent webpage on Access corruption:

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

I haven't seen Date/Time fields getting corrupted, at least not as a
specific symptom, but there's a lot of wierd things that can happen.
You might have some programmatic corruption in the DLL files that
handle dates; you may want to consider COMPLETELY uninstalling Office
(using a disk and registry cleaner, not just Microsoft's uninstall)
and reinstalling.
 
John Vinson said:
I have
Click to expand...
I haven't seen Date/Time fields getting corrupted, at least not as a
specific symptom, but there's a lot of wierd things that can happen.
Click to expand...

I've seen various fields get corrupted or entire tables. But not
specifically date/time fields.

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
 
Thank you for your assistance. I tried to import the data
into a new database, but it got only as far as the corrupt
table and expired. I then used jetcomp.exe; as this does
not open the table to compact, it went through ok. I was
then able to import the data into a new database. Funny
enough after this I was able to view the corrupt record
and then delete it; something not possible before as the
application would fall over when it got to that record.
Strange thing IT isn't it? But all is now well. We have
just got a problem with an Office 2000 upgrade error 1706
to deal with. If its not one thing its another!

Neil
 
Back
Top