Re: Mostly broken- Applescript + Leopard + Filemaker 6
Re: Mostly broken- Applescript + Leopard + Filemaker 6
- Subject: Re: Mostly broken- Applescript + Leopard + Filemaker 6
- From: Christopher Nebel <email@hidden>
- Date: Fri, 18 Jul 2008 12:15:34 -0700
On Jul 18, 2008, at 8:20 AM, Eric Geoffroy wrote:
I just discovered half of my FMP6 scripts are DOA in Leopard 10.5.x
Some
scripts won't compile, and the FMP6 dictionary errors when opened. I
probed
the ascript list archives and found a short thread several months old.
The last word from Chris Nebel was they're looking into it. Given
how old
FMP6 is, it probably isn't on the hot list.
Any update I may have missed? Workaround?
The only option seems to be hanging onto Tiger until our company
converts
the databases to FMP 9. This is unfortunate because my new Mac Pro
(Jan 08)
will not run Tiger.
In the immortal words of Ellen Feiss- "It's like, a bummer."
Ah, <radar:5598447>. Known, investigated, even fixed, but I can't say
when the fix will ship.
The problem has to do with how FileMaker is packaged -- it uses an
unusual mix of old- and new-style packaging, so AppleScript
(technically, CFBundle) thinks it doesn't have any resources, notably
a dictionary. I'd give you instructions for how to re-package
FileMaker, but FileMaker notices that it's been modified and refuses
to run. (I'm not ambitious enough to patch around that.) The best
I've been able to come up with is a re-packaged FileMaker that you
only use for building scripts -- use a "using terms from" block or be
careful about hiding the fake one before you run. Here's how to do it:
1. Make a copy of FileMaker Pro.app.
2. You'll need Terminal for this bit:
% cd [path to the copy here; just drag it from Finder into Terminal.]
% cd Contents
% cat < MacOS/FileMaker\ Pro/..namedfork/rsrc > Resources/FileMaker\
Pro.rsrc
That's your modified FileMaker. You can either name it something else
(I used "FakeMaker") and use a "using terms from" block to reference
it, or you can try this (which I haven't tried, but I think it'll work):
Every time you want to open Script Editor for editing FileMaker
scripts, do this:
1. Hide the real FileMaker Pro (archiving it and then deleting the
original works well), and put the fake one in its place.
2. Launch Script Editor, and open a FileMaker script. It should bind
to the modified FileMaker.
3. Restore the real FileMaker, putting it back in its original
location, and launch it. AppleScript will prefer running applications
to non-running ones, and should think that it's already gotten the
dictionary.
Even more alternatively, you could beat on FileMaker Inc. and try to
get them to release a patched version 6 that fixes this on their side,
but I wouldn't hold much hope for that. I assume that upgrading
FileMaker to a newer version is out of the question.
--Chris Nebel
AppleScript Engineering
_______________________________________________
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