January 29, 201015 yr What could be the matter if "Exit Application" does not work on an IPW page? I've had it as part of a longer script, then placed a button on screen with just that one script step attached: Exit Application. Nothing happens... Any ideas? Thanks!!
May 18, 201015 yr Author For anyone experiencing the same problem, here's some info. While FileMaker claims that IWP will skip an incompatible script step and continue executing the script in question, in reality it is much more likely to simply stop in the midst of the script. While no information is provided on screen in such event, the IWP log might help to find the incompatible step. In our case it was a corrupt file. None of the regular FileMaker functionality was affected, thus we didn't realize we were dealing with corruption until we published certain layouts with IWP. The Recover function (of course) didn't know of any corruption. Useless. However, rebuilding the IPW tables, scripts and layouts helped and the Exit Application script step now works. PS: FileMaker, we really need a way to (simulate) script debugging under IWP...
May 18, 201015 yr "While FileMaker claims that IWP will skip an incompatible script step and continue executing the script in question" Depends on whether Allow Abort is On or Off. If it's OFF, then the script step will be skipped, otherwise it'll Halt.
May 19, 201015 yr Author Well, in our experience that is wishful thinking. In most cases the script stops even when user abort was off and error capture on. It could be our set-up, however I've heard this from other sources too.
Create an account or sign in to comment