FileMaker Pro: Target Application Incorrect in Apple Event Command

This information was provided by Claris Corporation on 16 March 1998, and incorporated into Apple Computer's Tech Info Library.
[NOTE: It is recommended that you have the following versions of software: System 7.1.1 or System 7.5; AppleScript 1.1]

AppleScripting Level: Beginner

Q. I set up a script in FileMaker Pro 2.0 which has a "Send Apple Event" command. After choosing the Target Application, the wrong version of the application shows up as a parameter of the command.

A. FileMaker Pro 2.0 sends an Apple event to the Finder. The Finder chooses the correct application based on:

Type = 'APPL'
Creator = <the four-character code of the application chosen by the user>
Creation Date = <the most recently created application>

The third item in that list is what throws off the selection of the Target Application. Basically, no matter which version of an application you choose, the Finder decides which one to actually send the Apple event to based on which version on your hard drive is the most recent.

Solution: if you absolutely need to have the Apple event sent to an earlier version of a specific application (HyperCard 2.1 versus HyperCard Player is a good example), the only way to get around this is to remove the more recent version(s) from your hard drive before the Apple event is sent. Moving the more recent version to a floppy disk, even if the floppy disk is in the drive, allows the Finder to choose your originally selected version.

Corollary: if you choose an application on a floppy disk to be the Target Application, the application which the Finder will actually select is the most recent version located on your hard drive (even if the version on the floppy disk is more recent).

In practice: it seems unlikely that this situation will present itself often. It will most likely occur for HyperCard stack developers who have the Player on their drives and happen to set up a FM script like this (the HyperCard Player's creation date is more recent than HyperCard 2.1).

Corollary #2: Moving the more recent version of an application to another local hard drive other than the boot volume will not solve the issue.
Published Date: Feb 18, 2012