September 27, 201015 yr Hi, I finally decided to update an old FP5 application to FM11. This application consists of 45 files (some interface files, rest data files). I have got most conversion bugs ironed out and the application works fine in FM11 except for start up. In FM6 it took about 1 minute to open the application (opening all files, transferring user ID). Now it takes about 3 minutes. I realize I am not using an ideal design by having 45 tables in 45 files. However, rewriting the application was not an option. I tried to delay opening some files until a user accesses that part of the application. Unfortunately, this creates unacceptable delays during the actual use of the application. I already checked and cleaned up all file references, because I assume the long start up time is related to the many files and relationships in these files. Do you have any ideas how I can improve the start up procedure (i.e. open files hidden). Thanks, Joost Kingma Edited September 27, 201015 yr by Guest
September 27, 201015 yr Have you had a chance to review the "file references" that are stored in each database file, as part of the Manage External Data Sources? For databases long-in-the-tooth, it's common for multiple file references to have "built up" as a result of being deployed on different computers. FileMaker resolves these "paths" in the order they appear. If each file opens, then at least one of the File Paths does indeed "work," but FM may be having to resolve several "old" file paths before reaching the "right" one. Maybe it will help.
September 30, 201015 yr Author Yes, all file references are cleaned up, but it is still very slow. -( Joost Kingma
November 16, 201015 yr Author I did some more testing and found out that the opening time of a file is related to the amount of TO's in the file. I guess FM somehow checks the TO's when a file is initially opened. I have decided now to skip my opening script and delay the opening of the different files to the moment a user opens a module. The drawback of this approach is that a user experiences a delay when he/she opens a module for the first time. However I think this is better then having to 3-4 minutes until the application has started.
Create an account or sign in to comment