from your backup copy ( do you have it ? ) make a clone and import all the 15000 record from the damaged DB ( that must be trushed ).
It had find a solution to solve this question ,but I don't konw what happend.
Is it the bug of filemaker?
I have a database here with 8,000,000+ records, and records are added and deleted continually. There has been no bug reported regarding deleting a large number of records. If you force quit during the deleting, then that could definitely damage the file.
The solution by "raybaudi" is excellent. (Thank you!). That is, use the most recent backup, make a clone of the file, and import the 15,000 records from the backup file.
"That is, use the most recent backup, make a clone of the file, and import the 15,000 records from the backup file."
This isn't what I said...
In the way that you propose ( cloning the damaged db and importing into that clone the 15000 record from a backup copy ) leaves the corruption inaltered.
Sorry for the confusion. This is what I tried to say:
1. Use the most recent backup (that isn't corrupted)
2. Make a clone of the most recent backup
3. Open the the clone
4. Import the 15,000 records from the backup file in step #1 above.
Ok , TSGal
now we have said the same thing ;)
"4. Import the 15,000 records from the backup file in step #1 above."
This is not the same of what I said.
Who knows if there are those 15000 record in the backup ?
4. Import the 15,000 records from the damaged file