I am unable to edit a table

[Guest]

One of the records in the table got corrupted. I tried to edit the record but
got error message 3709 - 'the search key was not found in any record'. I
cannot save changes to the table whether made in the table directly or via
the forms.

 

[Steve Schapel]

Robert,

More questions than answers at this stage, I'm afraid. Do you have a
recent backup of the data? Are you able to compact the database? Are
you able to visually locate the corrupted records if you look at the
data in the table?

 

[Guest]

i wanted to join this discussion because i have what i believe to be a
similar problemo..

a user of my a2k mdb file (which sits on a shared network drive) sent me an
email on friday that they couldn't open it or something. when i came in
today, i got what i think was the same message and could (because of the way
mis installed a2k on my computer) access the repair facility which helped a
little. which means that the user could begin to access the mdb file but the
table behind the form which the user was needing to use had four records with
##### signs in all of the fields on each record. there is apparently no way
to delete these affected records from the table. so the user has re-entered
the affected data into the table, but i'm left wondering is there a problem
with allowing the table to exist in its current state and if so what ought to
be done about it?

thanks for any bandwidth!

-ted

 

[Steve Schapel]

Ted,

You should not allow the data to remain in its current state. Here's
what I would do...

1. Make sure you have a backup copy of the database.
2. Make a new blank table with the same structure as the problem table.
3. Look at the problem table and note the ID numbers of the records
either side of the corrupted records.
4. Make an Append Query based on the problem table, first of all
selecting all records before the corrupted records, and run the query to
enter the records into the new table, and then do the same for those
records after the corrupted records.
5. Compact the database.
6. Make a new MDB file, and from the File|GetExternal Data menu, import
all objects from the existing MDB.
7. Compact again.
8. To reduce the chance of future problems such as this, split the
database so each user has their own copy of the fronntend application on
the local machine, linked to the tables in a common backend file on the
server.

 

[Guest]

steve,

could you get 'round the append query by somehow cutting and pasting all
records other than the affected ones?

-ted

 

[Steve Schapel]

Ted,

I personally would never attempt to cut/paste Access data, although I
understand that it is possible to do so. Why do you want to do this?
Append queries are very easy.