COMPACTING AND REPAIRING DATABASE

[Ken Davis via AccessMonster.com]

I get this error message when trying to compact and repair my database:
(Could not find field "Description"). When I clicked on Help, the error message number comes up as (Error 3799) It's the first time I see this. Help anyone?

--
Message posted via http://www.accessmonster.com

[David Schofield]

On Mon, 24 Jan 2005 18:12:29 GMT, "Ken Davis via AccessMonster.com"
<fo***@AccessMonster.com> wrote:

I get this error message when trying to compact and repair my database:
(Could not find field "Description"). When I clicked on Help, the error message number comes up as (Error 3799) It's the first time I see this. Help anyone?

--
Message posted via http://www.accessmonster.com

Hi
All I can find is
"The table definition in one of the tables is damaged. ... First try
running the Access Repair option. If this doesn't work then you will
then want to extract all non-corrupted tables into a new access
database. Using the import option. Then reconstruct the damaged table.

(Or use a backup!)

David

[paii, Ron]

I am guessing that "Description" is a memo field.

Every time I had problems with Compact and Repair has been because of a
corrupted memo field. Confirm this by opening the table, page down though
the table looking for <Error> in the description field. "DO NOT" make the
corrupted record current, or Access will most likely crash.

If you have a backup, restore it and check if the corruption is in the
backup. If it is, you will need to recreate the table. Rename the damaged
table and create a new empty one. Copy the records up-to the corrupted one
using copy and paste. Continue looking at the old table for more corrupted
records. Cut and paste the good ones into your new table. Manually enter the
data from the corrupted records into you new table. Next rebuild your
relationships linking in the new table an unlinking the old. Note: make sure
all relationships are shown. You should now be able to delete the corrupted
table and run Repair on the database.

Others have posted that linking a memo field to a form can lead to
corruption. I have headed this warning and now use unbound controls for all
memo fields, then write out the data in the after update event. The result
has been no new corruptions of this type, where I used to get 1 or 2 a year.
"Ken Davis via AccessMonster.com" <fo***@AccessMonster.com> wrote in message
news:e7******************************@AccessMonste r.com...

I get this error message when trying to compact and repair my database:
(Could not find field "Description"). When I clicked on Help, the error message number comes up as (Error 3799) It's the first time I see this.
Help anyone?
--
Message posted via http://www.accessmonster.com

[ridsel]

I'm getting the same error, and yet I have no field called "Description" anywhere. I can't look through manually to find which table has the corruption, as many are 50k records long. Tips for finding the corruption location?

I am guessing that "Description" is a memo field.

Every time I had problems with Compact and Repair has been because of a
corrupted memo field. Confirm this by opening the table, page down though
the table looking for <Error> in the description field. "DO NOT" make the
corrupted record current, or Access will most likely crash.

If you have a backup, restore it and check if the corruption is in the
backup. If it is, you will need to recreate the table. Rename the damaged
table and create a new empty one. Copy the records up-to the corrupted one
using copy and paste. Continue looking at the old table for more corrupted
records. Cut and paste the good ones into your new table. Manually enter the
data from the corrupted records into you new table. Next rebuild your
relationships linking in the new table an unlinking the old. Note: make sure
all relationships are shown. You should now be able to delete the corrupted
table and run Repair on the database.

Others have posted that linking a memo field to a form can lead to
corruption. I have headed this warning and now use unbound controls for all
memo fields, then write out the data in the after update event. The result
has been no new corruptions of this type, where I used to get 1 or 2 a year.


"Ken Davis via AccessMonster.com" <[e-mail]> wrote in message
news:e7b4dc17de874df6a3f2b71858455084@AccessMonste r.com...[color=blue]
> I get this error message when trying to compact and repair my database:
> (Could not find field "Description"). When I clicked on Help, the error[/color]
message number comes up as (Error 3799) It's the first time I see this.
Help anyone?[color=blue]
>
> --
> Message posted via http://www.accessmonster.com[/color]