Quantcast
Channel: FileMaker Forum > Report an issue
Viewing all articles
Browse latest Browse all 3510

Some file operations in FileMaker Go requires a workaround (3 Comments)

$
0
0

Issue report by Mogens Brun

Product

FileMaker Go

Version

Go_iPad 13.0.5

Operating system version

iOS 8.1

Description of the issue

FileMaker Go will fail when the following two script steps are performed in sequence:
"Close File ["TestToDelete"]
"Export Records [No dialog; "TestToDelete.fmp12"]" (no fields specified for export)
Close File will return Error 13 and TestToDelete is not closed. Neither will the export succeed.

But if a Pause script is placed between the two steps, it will partly succeed:
"Close File ["TestToDelete"]
"Pause/Resume Script [Duration (seconds): 0,001]"
"Export Records [No dialog; "TestToDelete.fmp12"]"
TestToDelete will be closed and the export succeeds. However Close step still reports Error 13

Steps to reproduce the problem

I have created a small FileMaker 13 file (TestOfDeleteFile.fmp12), which demonstrates the problem. I will be happy to mail it, if I receive a mailing address (mogens_brun@me.com).

Expected result

If the above script steps are tested in FileMaker Pro 13:
"Close File ["TestToDelete"]
"Export Records [No dialog; "TestToDelete.fmp12"]"

(1) TestToDelete file is closed with Error = 0
(2) Export Records will delete TestToDelete with Error = 0

Actual result

If the above script steps are tested in FileMaker Go 13:
"Close File ["TestToDelete"]
"Export Records [No dialog; "TestToDelete.fmp12"]"

(1) TestToDelete file is not closed and returns Error = 13
(2) Export Records can't delete TestToDelete and returns Error = 3

Exact text of any error message(s) that appear

Se error codes above.

Configuration information

The uploaded screenshot displays results from two scripts (with and without pause) between file script steps and the result for running in FileMaker Pro 13 and FileMaker Go 13. The error code after each instruction is shown together with the file open (except the actual testing file).

Workaround

Placing a Pause script step between Close and Export helps: the actual file will be closed and next deleted. But Error 13 and 3 is returned respectively. (In FileMaker Pro 13 Export will return 410, because no fields are specified for export)

Screenshot


Viewing all articles
Browse latest Browse all 3510

Trending Articles