Re: FileMaker database access conflict
Re: FileMaker database access conflict
- Subject: Re: FileMaker database access conflict
- From: demski <email@hidden>
- Date: Thu, 31 May 2012 12:17:51 +0200
Hi, then maybe a simple try-Block might help?
In case of the Error of no permission just retry until you are allowed?
On FM Server you would have the same Dialog popping up in case of inaccessible Records...
Another possibility might be to have a FM-Script running the AS-Routine.
There you could directly catch the Error and deal with it in an appropriate manner!
hth,
demski
Am 30.04.2012 um 11:04 schrieb Marion Dickten:
> Hi,
>
>> On 30 May 2012, at 08:38, Marion Dickten wrote:
>>
>>> I am using AppleScripts to insert and delete records in a FileMaker database. Since this is a database other people access at the same time (remotely opened), we often run into access problems. Is there a way to create a database record that is locked for access except for the creating script? I have been thinking of transactions but what I've found by googling so far doesn't sound encouraging.
>>> (There are also some scripts created within FileMaker using FileMaker's own scripting language, and they give me the same problem.)
>>
>> Semi-random thoughts:
>>
>> - Are you using FileMaker Server to host the database? If not, this may help.
>>
>> - Are you creating the record via the script and then adding in data? Is this the problem? Have you tried creating the record with the data as a single action?
>>
>> - Can you not catch errors and retry?
>
> Well, as for using FileMaker Server, I would have to ask. I'm pretty much of a newbie about FileMaker and I simple use what I'm told to, I am only asked to do the AppleScripting.
>
> The problem is usually deleting a record, but sometimes it seems that inserting data is also a problem.
> Let me be as specific as I can. The database was created and is maintained by someone else. Most of the fields in the table are calculated by FileMaker scripts, sometimes rather intricate ones. The whole purpose of creating a new record is to insert one value into one special cell and have all the rest calculated. Then we pull the calculated values out via AppleScript and put them into another document. So the table is usually empty. We create a record, let FileMaker populate it, look at the results, and delete it again.
>
> The chief problem is that it is *not* an exception which interrupts the script, it is a regular dialog put up by FileMaker stating that we can't be allowed access because someone else is already accessing the data.
>
> Marion
> _______________________________________________
> 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
_______________________________________________
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