AnsweredAssumed Answered

Disabling a script step does not disable file references

Question asked by MogensBrun on Nov 16, 2010
Latest reply on Dec 9, 2010 by TSGal

Summary

Disabling a script step does not disable file references

Product

FileMaker Pro

Version

11.0v2

Operating system version

Mac OSX 10.6.5

Description of the issue

Disabling a script step (ex. Set Field [ Table_in_Another_File::FieldA ; 1 ] does not disable the reference to Table_in_another_file::FieldA.

Steps to reproduce the problem

If Another_File is closed when you in Manage scripts open a script with only one script step:
// Set Field [ Table_in_Another_File::FieldA ; 1 ]
then Another_File will immediately be opened (DatabaseNames in Data Viewer) will report it.

Expected result

As the script step is disabled you would expect the text after // to be inoperative. However, it turns out that it is only partly inoperative.

I noticed, because I had trouble closing a file (Another_File). First when I removed disabled lines with reference to this file, would the close function actually close the file.

Actual result

Another_File is not able to close if there is a disabled script step like Set Field to a related field in Another_File. Deleting the disabled script step will allow a close script step to Another_File to work.

Exact text of any error message(s) that appear

There is no error report, but you can follow open files in Data Viewer with DatabaseNames

Outcomes