importing scripts

[Paolo]

I need to substitute a script with an imported one.

I delete the old script, import the new script and then rename the new script to match the name with the old one.

However when I delete the old script any reference to it is lost, and not re-established even when a new script is created (or imported) with the same name.

Is there any way to work around this ??

Thank you

[RussBaker]

Filemaker allows you to have multiple scripts with the same name in a file - so naming a script the same as the one it replaces willl not automatically transfer over.

AFAIK, there isn't an automatic workaround to this. BUT (caution - inelegant solution follows) if you have your "old" script called by heaps of buttons and don't want to go through your file(s) changing each one, then you can leave your old script in place and edit it down to a one step script which simply calls the imported script using the Perform Script[subscripts} step.

[LiveOak]

I'm not past using this technique on any given day! Another good reason to break larger scripts into subscripts. If you replace a subscript, the may be fewer reconnections to do and they are all from within ScriptMaker.

FM keeps track of scripts by an internal number, the same as it does for fields, relationships, value lists, etc. This allows duplicate names (not fields) and renaming without disconnecting things. Files are the one case where FM has to use names and renaming does result in disconnecting (or reconnecting) files.

-bd