AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Filemaker pro 14 hour alert9/6/2023 Although, you can check all your calculations and script steps manually, not only will that take you a really, really long time for any complex database, but the likelihood is very high that you will miss at least one little problem that produces troubleshooting headaches for you in the future. It will be you’re friend throughout this process. I can’t stress enough the importance of reading the little Import.log file, whether you do it manually or using the Import Log Interpreter tool. Alternatively, you can use the Import Log Interpreter tool to easily browse through the import results, see exactly what was imported and see the errors associated with each object in an easy to read format. Open this file and scroll to the end to see the results of your import and whether any errors had occurred. We don’t want to have to fix “” errors in our calculations. We do this now in case custom functions are referenced in calculated fields or script calculations. If there are any custom functions in the source file that do not exist in the target file, copy or import them from the source to the the target file. You don’t want to have to go through each layout and script and fix all of the “” or “” errors manually.Īt this point, you are not copying any fields or tables yet, you simply want to make sure than any of the table occurrences and fields that already exist in your target database match the corresponding table occurrences and fields in the source file (the one you will be throwing away). This way when you copy scripts and other objects from one file to another, it will properly map the tables and fields. The main idea behind this step is that you want to make sure that the two files have matching table occurrence and field names. ![]() Step 1: Rename table occurrences and fields
0 Comments
Read More
Leave a Reply. |