Difference between FileMaker Pro 13 and FileMaker Go 13 regarding Manage External Data Sources (1 Comment)

Issue report by Mogens Brun

Product

FileMaker Go

Version

13

Operating system version

iOS 8.1

Description of the issue

If a FileMaker Pro file deletes an external FileMaker Pro file (by Export Records with no Field Order for Export specified) and a new FileMaker file with the same name as the deleted file is created (exported), the current FileMaker file will be able to call at script in the newly created FileMaker file.

But this is not the case with FileMaker Go. If a FileMaker file, which is referenced by Manage External Data Sources, is closed, it is not possible to Open a file with the same name or make a Script Call to it.

Steps to reproduce the problem

I can send a FileMaker Pro 13 file, which demonstrates the problem. Please inform me about the mail address, I must use.

Exact text of any error message(s) that appear

There is no error in FileMaker Pro, In FileMaker Go 13 error 100 will be reported.

Workaround

A workaround is to create 2 instances of External Data Sources to the file to be deleted and called again. Until the external file is deleted External Data Sources 1 should be used. After deleting the external FileMaker file External Data Sources 2 should be used.