Using FMD 5.5 on PC ME O.S., In the process of building my Filemaker application I used external scripts. The script call has embedded the IP address of the machine I used to create the application.

'Perform Scipt[subscripts,External:"TestA.FP5(10.15.15.3)"]'

No matter how I chose this external Script, with 'Save relative path' checked or unchecked it still maintains the IP address.

Further if a runtime solution is created, the RTS shows exactly the same address, if opened with filemaker.

When the solution is now installed on a different network, it is looking for the IP address of the machine associated with the file, which is considerably slowing down the opening of the solution.

Any thoughts on how to force it to open the files on the machine it was installed on.

(We do not intend to run Server with this solution.)

You could try changing the names of the files in the solution with the "FileMaker Developer Tool", that comes with FileMaker Developer 5.5. When changing the file names with this tool, it updates internal references for all files.

I am not certain that this it will get rid of "old" references, but that's what I would try anyway!

I would change all file names from "x" to "x1" and then back again to "x" just to make sure that it updates the references.

I've once had the same problem as you, that the timeout seemed to be awfully long, but that was on a clients' network with FM Server. The culprit in that case was a feature in their Novell network. The client workstations was set up to use some new "locator protocol" which made FileMaker wait up to 2 minutes before it timed out and found the correct IP address! We switched it off and things went much faster.

How much slower is your solution running?

Daniel

[ March 11, 2002, 05:10 AM: Message edited by: DanielS ]

It is taking at least 45 sec to find each external script. Thanks for the input, will experiment.