Access compact & repair problem

[JASON VERNON]

While compacting my Access Database I received the
following message; COULD NOT FIND FIELD 'DESCRIPTION'.
This message gives the option of clicking ok, which when
clicked ends the compacting process and returns me to
Access. If I continue working in Access I will eventually
receive a message telling me "database has been corrupted
and needs to be repaired." I'm given the option to repair
now. If I select yes the repair seems to work and I'm
allowed to continue working in my database for a time
until the "Database corrupted needs to be repaired"
message returns. Currently I'm caught in this corrupt &
repair loop. I believe this has something to do with the
orriginal "could not find field 'description'" error.
Anyone have any idea how I can correct this problem?

 

[Grumpy Aero Guy]

My direct answer is: no, I don't know what's causing it.

Try creating a new blank database, and importing all of your objects from
the old db to the newly created blank db. THEN try it.

My guess is that will make it work ok.....

 

[Van T. Dinh]

You got corruptions in your database.

See Tony Toews' article:

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

 

[Tony Toews]

While compacting my Access Database I received the
following message; COULD NOT FIND FIELD 'DESCRIPTION'.

1017 - "Could not find field "Description" It's possible the problem
is with a table that has a self-join and Memo fields, and has
referential integrity enforced. ACC2000: Table Corruption After
Referential Integrity Checks - 296389
http://support.microsoft.com/?kbid=296389
But it's more likely to be a sign of corruption.

This message gives the option of clicking ok, which when
clicked ends the compacting process and returns me to
Access. If I continue working in Access I will eventually
receive a message telling me "database has been corrupted
and needs to be repaired."

Definitely a bit wield. Please let us know what solves your problem.
Either the importing into a new MDB or following the steps in the KB
article or something else.

Thanks, 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

 

[Sylvain Lafontaine]

I solved something remotely similar like this last year by using the switch
/decompile: create a shortcut to your database, add this switch and give it
a try.

But if I where you, I would first try the suggestion by Frank Bachman to
import all of your objects into a blank database; just in case that some
manipulation make things worst.

S. L.