koen on 27 Jan, 2014 03:30 PM
The example plug-in is probably based on a plug-in template that
FileMaker provides with FileMaker Pro Advanced. It was probably
compiled and maybe altered by the person who wrote your original
Mpl_StartScript( Get ( FileName ) ; "sAdd Customer to Invoice"
When this function is executed, it will ask FileMaker to run the
script "sAdd Customer to Invoice" in the current file. But as you
stated earlier, there is no script with that name in your solution.
Scripts can never be part of a plug-in, so the script can't be
hidden in the plug-in.
The plug-in was used in the past, when script triggers didn't
exist, to trigger a script when a field was changed.
Our free plug-in DoScript has the same functionality. You could
replace the code by using
mFMb_DoScript( "sAdd Customer to Invoice" ; Get ( FileName ) )
But if none of the scripts exist that the plug-in wants to
trigger, I would just disable the plug-in calls, because they have
no use in your solution.
Can you send us a version of the MacExample plug-in, so we can
further investigate why it is conflicting with our plug-in?