Hoke

ah, slight problem with that detail... Thanks for the solution, though... I was hoping it was something that easy to do.

It is a function in the MacExample plugin. On the CD, not installed by default, I think /Filemaker Developer 7/English Extras/Examples/FMExample/FMPlugInSDK/Example/MacExample.fmplugin description is on p 61 of the Dev Guide; includes source code and what-not on disk, but that's beyond me

Hi- I just received the Developer 7 version, and I was very pleased to see the StartScript external function. It seemed like a good way to add trigger like functionality, but I am at a bit of a loss to figure out a way to pass any context with the script invocation. It would seem to me that this function would be really good if you could also set up the script parameter when calling it. For example, I have an interface database (no tables) that file references the tables in another database. I made a calculated field to invoke the script. Now when I change the field in the interface file, the script will run but it will use the current rec of the tables database, not the interface file. If the function was StartScript(fileName, scriptName, scriptParameter) so that I could tell the script which record I wanted to process, then it would be easy. So here is the question... any of you C gurus willing to whip up a plugin like this? Is there some technical reason that this isn't feasible? FileMaker Version: Dev 7 Platform: Mac OS X Panther