Re: FileMaker database access conflict
Re: FileMaker database access conflict
- Subject: Re: FileMaker database access conflict
- From: Chris Paveglio <email@hidden>
- Date: Thu, 31 May 2012 12:58:09 +0000
- Thread-topic: FileMaker database access conflict
This was a known problem (well maybe sort of unknown?) that started in FM11,
not 12.
Applescript commands run asyncronously (that is, many commands can run at
once, as fast as they get dished out by a script) instead of syncronously
(where one command would run and have to finish before another command is
accepted).
I believe this is your problem, and Marion is correct, the only way to
overcome it (that I've read about) is to use delay commands (or do shell
script 'sleep 2') to give the first script command time to complete.
Or, you could try to re-write your Applescripts into Filemaker native
scripts (though obviously you can't get all the same functionality, but
there are variables in FM scripts now that can help to a certain degree).
Let all your FM friends know about this issue! I've had to point this out to
this list and others several times before.
Also I've read that FM12 is really slow with list display, like 10x slower
than earlier. Check some FM forums for comments on it.
Chris
On 5/31/12 6:09 AM, "email@hidden"
<email@hidden> wrote:
> I, too, have been experiencing this problem since upgrading to FileMaker 12. I
> use a FileMaker database with scripts that populate data with values from SQL
> queries, pull the data, and then I also delete the record. I upgraded from
> FileMaker 10 to FileMaker 12 a couple weeks ago, and have been getting this
> random error ever since. We do use FileMaker server, and while I'm not sure
> exactly what is happening, I have been able to reduce the occurrence by
> inserting delays after the scripts and SQL queries, before switching tables
> with 'show window', etc..
Maybe try inserting 'delay 2' after your scripts,
> just to give FileMaker a chance to catch up, before moving on. Like Simon
> suggested, you could also use 'try/on error'. I know this isn't a very elegant
> solution, and I'd love another myself, but this seems to be working, for now.
> Your 'someone else is already accessing the data' error might not actually be
> someone else at all. It could be your computer attempting to access the table
> while a script is still running. I am the only person who ever accesses the
> particular table I'm referring to, and as I said, I have been getting this
> error since the switch to FileMaker 12.
The odd thing is that this error
> seems to be related to scripts taking longer to process with FileMaker 12.
> While most things seem faster with 12, are scripts taking longer to process,
> or is FileMaker 12 just dealing with them in a different manner than it did in
> FileMaker 10?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden