In almost all cases this solves the problem without Recover. What's that? First of all: Don't Panic! Before you follow that dialog's advice, go back to your previous FileMaker Pro version, open the file and save a Compacted Copy - then try again with FileMaker Pro 9. With the advent of FileMaker Pro 9.0v1 some users are confronted with a dialog like this: The description is moved in here when a new update has resolved that bug. There are special upgrade conditions for existing customers at our web shop.From time to time some bugs slip into a FileMaker Pro release. It can be upgraded by purchasing a license number from within the application or at our web shop. all names and IDs are shown as asterisks (*). The free version shows the first 5 differences of every section, the rest is listed 'anonymously' i. It shows the exact number of changes that were applied to specific sections within the structure.ĭownload FMDiff for your platform. At one and the same time the programmer and the customer have a means to prove and inspect the progress at regular intervals. SOX (Sarbanes-Oxley) Compliance AuditorsįMDiff serves to document an ongoing solution development.The short answer is: anyone who is in charge of ordering, developing, hosting, maintaining, or auditing FileMaker solutions will need FMDiff. How many times and with what platforms, system versions, FileMaker Pro or Server versions has a file ever been run? This helps to track down version related errors. Has a file ever been Recovered? How many times? This is very important to judge about the quality and sanity of a solution. (Unfortunately this information is no longer logged within the file since FM 12 and hence can't be shown. This time stamp serves to identify "an original" and is a means to prove ownership.įMDiff Unveils The Recover Count and lists System and FileMaker Versions used with the file ^ When was the file originally created? Every file stores an internal time stamp that does never change when a file is Cloned, Recovered or Copied. The combination of keeping a good copy (one that never crashed) and using FMDiff to compare it against the installed solution can be considered the best possible security measure.įMDiff Unveils The Original Creation Timestamp ^ This is something that even the native FileMaker Recover command does not always straighten out, which may lead to subsequent malfunctions or crashes. The licensed version of FMDiff even performs additional tests for ascending IDs and correct block lengths. While comparing it checks the file's structure to be "well-formed". You even may compare files in environments where the original configuration does not exist, like ODBC, JDBC, ESS, or devices (camera) are not connected.įMDiff knows whether your FileMaker Pro files are still intact. You are able to document the progress in development or unauthorised modifications by someone else. Files of the same type can be compared against each other. FMDiff is able to read FileMaker files of type. This is especially important for sensitive areas like accounting or healthcare. For the first time it is now possible to verify that the internal file structure (tables, fields, relations, etc.) is the same as at the time of delivery. You immediately learn whether anything has changed and where, either due to human, hardware, or software error.įMDiff compares your current solution against a previous one and reports the differences. Simply compare your backup or "Good Clone" against the solution. With FMDiff the basic test is done within minutes. If your solution suddenly exhibits strange behaviour, how do you find out what happened to the files? How much time would you have to invest to find out? Would it be possible at all? FMDiff Compares FileMaker Pro Files And Lists Differences ^
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |