Record This Index can NOT be repaired. If a Record (that would otherwise be lost) can be shown through a Find or Go to Related Record, Export it to a new table or file, delete it in the original table, and then re-Import it (auto-enter option off!). The original data is rescued although it now has a new Record ID. This problem almost never appears though.
So, I've done this already. This article does not mention anything about not being able to delete a record.
Sorry for not being precise. aDid you re-import to a new table? Deleting the old table also removes invalid records and indexes.
Deleting a whole table? Yikes!
Creating new tables to overcome bad data seems a little extreme? This would mean re-creating hundreds of fields!
I could try copying and pasting tables, but I supect this would just copy the problems...?
What you saw was not weird
it's just that you can not delete a "phantom" record by hand, since it does not really exist
FileMaker has simply lost track of your records
see here as well, under "Phantom" Records:
Importing into a clone is the only ( and sometimes painful ) solution
If it's just an index problem, re-indexing is not so bad
and yes, this can be a recurring problem
> There was one record, full of question marks, so I deleted it and imported the data for that record from a merge file exported from a backup of the database.
All was well with the newly created record, until the user searched for the record and found 2 of the same- the first one was the original record with the question marks on it, the second one was the newly imported record.
Weirdness continues, because I tried to delete the question mark record and the record dissapeared, but the number of records does NOT reduce and when you search for the record, you get both.
Greg is right. Import into a clone of the file is probably the least expensive method. You may import the native FileMaker format.
You didn't say what FileMaker version your customer is running and whether it is on FM server. Errors like that may happen when FM quits unexpectedly.
I have already imported the data into a clone using the filemaker format, this seemed to fix the problem for a short time. Now I think I'll try it with merge files.
They are running v12 on server.