I recently upgraded FileMaker to version 11, and discovered that my
python-based application that relies on appscript to control a FileMaker
database has broken.
If I use appscript to ask FileMaker 10 to tell me about the application class,
I get this:
>>>> fm10.help('-t application')
> ==============================================================================
> Help (-t application)
>
> Reference: app(u'/Applications/FileMaker Pro 10 Advanced/FileMaker Pro
> Advanced.app')
>
> ------------------------------------------------------------------------------
> Terminology for application class
>
> Class: application -- The application
> Plural:
> applications
> Properties:
> best_type (r/o) : type_class -- The best descriptor type
> class_ (r/o) : type_class -- The class
> default_type (r/o) : type_class -- The default descriptor type
> frontmost (r/o) : boolean -- Is this the frontmost application?
> name (r/o) : international_text -- The name of the application
> version (r/o) : version -- The version of the application
> Elements:
> documents -- by index, name
> windows -- by index, name
> databases -- by name, index
> menus -- by name, index
If I do the same with FileMaker 11, I get this:
>>>> fm11.help('-t application')
>
> ==============================================================================
> Help (-t application)
>
> Reference: app(u'/Applications/FileMaker Pro 11 Advanced/FileMaker Pro
> Advanced.app')
>
> ------------------------------------------------------------------------------
> Terminology for application class
>
> Class: application -- An application's top level scripting object.
> Plural:
> applications
> Inherits from:
> item (in Standard Suite)
> Properties:
> class_ (r/o) : type_class -- The class of the object.
> properties : record -- All of the object's properties.
> frontmost (r/o) : boolean -- Is this the frontmost (active) application?
> name (r/o) : unicode_text -- The name of the application.
> version (r/o) : unicode_text -- The version of the application.
> Elements:
> documents -- by name, index, relative, range, test
> windows -- by name, index, relative, range, test, id
Notice that with FileMaker 11, there are no databases or menus listed as
elements for the class 'application'. (There are other differences too, with
the properties.) Having no database element accessible from the application
object causes my scripts to fail. It may be that the dictionary has been
reorganized and these objects are somewhere else now.
Some test Applescripts I wrote with the Apple ScriptEditor work, so I don't
think it is a problem with the FileMaker 11 dictionary per se.
Any ideas? I'm not familiar with the appscript internals to even know where to
start.
John Jackson
John Jackson
_______________________________________________
Pythonmac-SIG maillist - [email protected]
http://mail.python.org/mailman/listinfo/pythonmac-sig
unsubscribe: http://mail.python.org/mailman/options/Pythonmac-SIG
