It has recently come to our attention that some applications install versions of the 'ObjectSupportLib' which cause several other programs (including FileMaker Pro) to stop handling Apple events. In this event, formerly functioning Apple Scripts will now generate an error. Reinstalling an appropriate version of the OSL should solve this issue.
Specifically, if you have installed the America Online 3.0 Evaluation software, it has installed a version of the OSL (v 1.1.1) which breaks our AE handling. OSL 1.1 does not have this issue.
What exactly is the issue?
Following Apple guidelines, FileMaker Pro checks with the Gestalt Manager to see that the ObjectSupportLib is indeed installed on the given machine. If the OSL is available, the event is passed along to FileMaker Pro, and the magic happens. This occurs whenever an Apple event is sent to FileMaker Pro (except when the application is launched from the Finder).
This is all well and good, except that the specific version of the OSL that is being discussed does not register itself with the Gestalt Manager. Hence, whenever FileMaker Pro receives and Apple event, it needs to be sure that the ObjectSupportLib is available. To do that it asks the Gestalt Manager if the OSL is around. The Gestalt Manager will always report that the OSL (at least version 1.1.1) is NOT available, and so the Apple event will NOT be handled.
It has been suggested that if an application NEEDS OSL 1.1.1, you can have DUAL FUNCTIONALITY if you install the appropriate version of the OSL in the given application's folder. In other words, if America Online 3.0 absolutely REQUIRES that OSL 1.1.1 be available to it (and we know that FileMaker Pro 3.0 needs OSL 1.1) you could put the OSL 1.1.1 file in America Online's application folder (right next to the application itself) and the OSL 1.1 file right into the FileMaker Pro 3.0 folder (ditto). We only offer this as a suggestion, as we have not tested this option.
If this does not work for you, or this is simply not a viable option, you may need to simply determine which application has a greater need for AppleScript in your given situation.