Runtime Access Very Slow

[EllenG]

I've been using Filemaker for some time now (since FMP3), but this is my first experience with Developer. When I create a runtime solution, it seems to run fine on my PC, but when I load it to another PC, even if that PC is faster and has more disk and RAM, it takes forever to open the application. It appears to be opening when clicked (hour glass blinks), then the hour glass disappears (returns to normal cursor). About 20-30 seconds later, the application opens. Sometimes it takes trying to open it twice.

Anyone have this problem? Am I doing something wrong. (I read the instructions for installing a runtime application and I think I'm doing it right!)

Another problem I'm having: I have an import script that imports records from Excel. The Excel file will allows be in a specific folder. In my non-bound program, once I set up the import, it continues to work great. However, when I bundle the solution, the import does not work (it seems to not be able to find the file.) Any ideas??

Thanks.

[kenneth2k1]

Hi:

My runtimes tend to take longer than I would like for them to open. But this is more like 5-10 seconds. Not 30.

I would look at your start up procedure. Do you have a start up script? Or were there plug-ins that the regular solution used? Do the runtimes come with records, are there loops or indexed procedures?

As far as the import problem, the path is stored in the file. Let's say you take that file to another PC, it won't be able to find that path. So it should prompt you. It should be ok for the same PC. What I like to do is put files in the solution folder, and all my functions point to that path. No matter what PC it's on, the solution folder can always be found.

You'll have to rephrase "The Excel file will allows be in a specific folder." That sounds like translated Russian.

Ken

[EllenG]

Thanks, that solved my Import problem. It works OK now, as long as I have the user specify the file. I did find a few other "problems" that I fixed, but it is still taking more then 10 seconds to open when installed on another PC, but only about 2-3 seconds to open for me.. Anyone know WHY that is?