Error -10011 : <MyFile> got an error: Data is being accessed by another user, script, or transaction.

[cincin]

Hello,

FMP Dev 6.0v4, Mac OS 10.4.4

In my main solution I have a simple FMP script that preforms an AppleScript if Status(CurrentPlatform) = 1 or -1:

tell application "Timer"

	open "Timer.clm"

end tell

Where "Timer" is a FMP 6.0v4 runtime file and "Timer.clm" is the related runtime FMP file with a custom extension.

Basically this is meant to open the separate FMP runtime "Timer" from my main solution.

It works perfectly before I turn my main solution into a runtime.

Once the main solution is compiled however, the script returns the following error message:

got an error: Data is being accessed by another user, script, or transaction. (Error -10011).

Where is the name of my main solution file.

The "Timer" runtime does not open. The script returns this error no matter what.

Any idea ?

Thanks to all

Cheers

cincin

[cincin]

Hello,

Here I am answering my own post again :

After some more testing I found a way to make it work, not sure exacly why it does work, but it does.

So in order for an AppleScript inside a runtime to be able to open another runtime without getting that pesky error message:

- The extensions of the two runtimes should be different

- There should be a single copy of the runtime being openned by the AppleScript on the computer, including in the trash.

Those are assumptions but changing the extension and making sure there was a single copy of the runtime being called by AppleScript solved my problem.

Hope it may help someone else...

Cheers

cincin

[Søren Dyhr]

Wounldn't it be much easier to make a compiled applescript called via the send event. Unless you deliberately violates the licensing issues on networking ...note that even making CGI's are strictly forbidden.

What it seems like is this:

http://www.fmforums.com/forum/showpost.php?post/138841/

--sd

[cincin]

Hello Soren,

Thanks for your input :

I don't see how it would be easier than having the script in the FM file, and having the AppleScript in a separate file just adds one more file for the end user to mess with...

Besides, my own reply states that it's all good as long as the extension is different and that there's only a single copy of the runtime being called.

But I appreciate you taking the time to suggest.

Cheers

cincin

[Søren Dyhr]

BTW could it also boil down to an uncommitted record, it is so that before executing the script in the other runtime be sure to make a Go Field[] in the first runtime followed by the AS that calls the execution in the other one. Letting the cursor stand in a field during a call from an applescript causes such errors.

--sd