However, in our opinion, the latter lacks some possibilities. We have mentioned here the impossibility to resume a FileMaker script that would be paused, but there is also the absence of possibility to differentiate the called script (callback) according to success or failure. This article develops this last point and provides a solution.
No library is necessary, but I had to write my own class that extends a bit FileMaker.PerformScript to FileMaker.PerformScript ( scriptName, parameter, successCallback, errorCallback ).
In fact, it all boils down to this: “FileMaker, call this script. If it went well do this, if it went badly do that”.
So in the calendar, here’s what really happens:
FileMaker does its job and decides if it wants to tell the Web Viewer if it went well or badly.
The Web Viewer executes the pieces of code (saved in step 1).
In code :