This file ran for a week before the corruption was discovered. It was damaged when it was copied to an IMac with a faulty hard drive. a file that runs fine, until you save as clone, and you find that three layouts are missing in the clone copy.This file ran for a full year before the corruption was discovered ( All the backups were corrupt ) a file that crashes only when two guests are on the same list layout, and a script is triggered to set a number field.But, It should go on to say that "problem" objects CAN often be edited, or deleted, in the Original file going forward ( or ignored, if of "low severity" ), and that Recover CAN actually repair certain problems, going forwardįileMaker Pro, and FileMaker Server will open and run files that are corrupt. It reminds you to check the log for "problems", and their "severity", and that the Recovered file should NOT be used going forward. Let me start out by saying that since FileMaker 10, Recover's closing "WARNING" is a bit misleading, and very unsettling. ![]() The following information is based on my experience as a FileMaker developer, FileMaker's TechInfo Knowledge Base, and on numerous discussions with FileMaker Tech Support, and FileMaker's Engineers. FileMaker Damaged Files, Corruption, & RecoverÄamaged Files and Hidden Corruption in FileMaker Pro ( A Guide to "Recover" )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |