AnsweredAssumed Answered

Importing Custom Functions from an open database can fail

Question asked by jjackson+fm@pobox.com on Aug 23, 2010
Latest reply on Sep 27, 2010 by TSGal

Summary

Importing Custom Functions from an open database can fail

Product

FileMaker Pro

Version

11.0v2

Operating system version

OS X 10.6.4

Description of the issue

If you have a set of custom functions that refer to each other (ie, custom function A calls B, which calls C, etc.)

and

you import them into a new database, from an existing database that is currently open, the import will succeed and report no errors, but actually can be silently failing. If you look at the functions, you will see either , or the entire function's contents commented out.

If this can't be fixed, disable imports from open files!

Steps to reproduce the problem

See the description above.

Expected result

I would expect if an import happens, and any changes are made to the incoming function, either by commenting out the code or inserting then this should be both logged and reported as an error.

If this can't be fixed, disable imports from open files!

Actual result

Nothing gets logged, and no errors are reported.

Exact text of any error message(s) that appear

None.

Workaround

Close the file you are importing from solves the problem.

Outcomes