I have a robot computer that does some importing/exporting chores between servers. Every so often I get a dialog box warning me of errors importing.

I though I had pretty strenuously set the error capture to on before and off after the import routines. My routines are error forgiving and will retry. As long as there is no dialog box waiting for an OK.

Is there still a plug in or some other solution for un-attended dialog box dismissals?

I am running FMPro 10 on a Mac Mini with OS X 10.5.7

My Robot is a file that is hosted on FMP Server 10.

I used to use OkeyDokey Pro but alas, there is no Mac OSX version to dismiss these messages.

First, try generating a database design report; that will dump all scripts; search this for any instances of set error capture OFF; that will show if you're ever turning it off, and you can remove those steps.

Second, at the beginning of each script which is running, add a line, to set a global field equal to the name of the script that's running, and put that field on a layout. Then when the error occurs, you can go to this layout and look what's in that field to show which script is running at the time the error occured. Even better is to implement formal logging in a separate table. I sell books online, and my solution interacts with web pages and services intensively; the log table records failures to login to sites, etc, making it much easier to debug problems in my solution.

Also with Applescript you can run a script at intervals to, say, check the timestamp of a file indicating when script last ran; if it didn't run, send filemaker a RETURN key, close Filemaker and re-start it, etc.

Error trapping in Filemaker is abysmal; not only does it not inform you which script and step caused an error, it does not allow you to run a script when an exception occurs.