Thank you for the post.
If recovery modified the file, then the recovered copy can still be corrupted. Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
1. The recovered copy may behave differently even if recover reports "no problems found."
2. Recover does not detect all problems.
3. Recover doesn't always fix all problems correctly.
4. Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledge base article that you may find useful: What to do when your file is corrupt (KB5421).
For more on the phantom ? records: Phantom Record, damaged file message, Recover can't detect a problem
This is one of many acknowledged bugs that can be found in the Known Bug List thread here in the Report an Issue section of the forum.
It can also be downloaded as a database file from: https://www.dropbox.com/s/jt09b82i0xijbu3/FMP%20Bugs.zip
I have all ready read the material at the links provided in the replies above. I realize there is a know bug regarding phanotom records and I also know that it is at it's core an indexing issue. What is NOT mentioned or discussed in any way is how records go from normal to phantom and what to do to prevent it from happening in the future.
The database has been working fine for several weeks since we did the recover. All of our scripts were running flawlessly then on July 5th existing records became corrupt (turned into what you call phantom records) right in front of someone. As he sat looking on each fields data disappeared and was replaced with a ?.
Some new information I just recieved today is that since that data corruption on July 5th none of the scripts are running. They start and then time out saying " Waiting for other process to finish..."
Here is the log entry:2013-07-14 21:31:47,717 (6356:root) [DEBUG] *** Running btcmain.py2013-07-14 21:31:47,717 (6356:root) [DEBUG] Loaded config from "z:\database\fmbin\config\btc.ini"2013-07-14 21:31:47,717 (6356:root) [INFO] Waiting for other process to finish...2013-07-14 21:35:44,250 (7024:root) [DEBUG] *** Running btcmain.py2013-07-14 21:35:44,250 (7024:root) [DEBUG] Loaded config from "z:\database\fmbin\config\btc.ini"2013-07-14 21:35:44,250 (7024:root) [INFO] Waiting for other process to finish...
This appears to be random. I can't have my clients data radomly disappearing and becoming permanently replaced with ????
A little more help is needed here.
I hope you have fixed the corruption issue with your FileMaker database. I ran into the similar issue and found a recovery software that restored all my data.
You could use this product in future, if you have face similar problem.