Filemaker + Frontier + OSX

[sdevore at mac.com]

I have seen problems with filemaker stability since os 10.2 directly 
from apple scripts, noticeably doing calls that contain "whose"  I have 
sent crash logs and bug reports to them, and have also seen similar 
reports on the apple-script list hosted by apple


Sam D
On Wednesday, December 11, 2002, at 08:30 AM, Tom Spivey wrote:

> Hi Nick,
>
> thanks for your answer, hopefully the right eyes read these mails...
>
> It is the classic situation, where you pay two companies quite a lot of
> money and none of them takes the responsibility for the problems.
>
> I wonder why Apple seeds OS X software to them, if they don't care...
>
> Below solution does not work for me, because I think it is considerably
> slower and I would have to use semaphores to block other requests...
>
> Well, today Filemaker released Filemaker Pro 6.0v4, but I have the 
> German
> version, which is not available right now...
>
> I'd be grateful, if you or anyone on this list could check if things 
> have
> improved. I read that some AppleScript things have been fixed - like 
> the
> count verb etc.
>
> Thanks
>
> Tom Spivey
>
>> First, the problem is probably 10.2.2. Apple broke something in 
>> 10.2.2;
>> my copy of Frontier stopped doing apple events, too, and I had to go
>> back to 10.2.1. There's a new beta which is supposed to fix the
>> problems with 10.2.2.
>>
>> I also haven't been able to use getData effectively. Even under 
>> 10.2.1,
>> I found it crashed or was unreliable. So instead I use:
>>
>>
>> delete(request[all]);
>> create (request);
>> setData(window[1].request[1].cell["Archive"], curImage);
>> find (window[1]);
>> dbRow = getData (record[first])
>>
>> It's slower but it works.
>>
>> But let me also echo your frustration. For me, Frontier's interaction
>> with other programs, mostly Filemaker, via Apple Events is one of its
>> main attractions and essentially my prime use for it. But it's always
>> the first thing to break with every change in OSX or Frontier. That's
>> obviously not always Frontier's fault, but it's a real drag. For the
>> relatively small tasks I am doing, it's not a big deal that Filemaker
>> find requests slow down the process, but that would be different if I
>> were doing large batches. I can't test the suggestion that the fault 
>> is
>> Filemaker's, because I didn't feel like writing an applescript which
>> would duplicate what I'm doing in Frontier to see if it was more
>> robust. If someone else could verify that it's Filemaker's fault, 
>> maybe
>> Filemaker would be persuaded to fix it.
>>
>> Good luck,
>>
>> Nick Cahill
>
>
====================
Samuel C. DeVore    sdevore at teachesme.com
www.TeachesMe.com
Because if you are not managing your content...
Who is?
See us for content management for teachers/schools/students
=====================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 2758 bytes
Desc: not available
Url : http://lists.userland.com/pipermail/frontier-users/attachments/20021211/479960a4/attachment-0002.bin