Hi,

I have a solution, which works together with another windows application (it generates data to be imported into FM, created by another developer).

The database communicates certain conditions (for example, data import succesful) to the other app. through simple exported text files created by FM scripts.

In most cases this works fine, but sometimes, when the database first opens the external application and the user instructs it to do its thing, and while the external application is running (this can take a couple of minutes), the user switches back to FM and presses for example Enter, an error box appears - while this dialog box is active, FM does not execute any scripts (that would generate the feedback text files for the external application)

Although this something the user is not supposed to do, they still do it occasionally. Is there a way to suppress these error dialogs or to force scripts to run no matter what?

Any ideas are greatly appreciated,

Jari V

Do you have in your script:

Set Error Capture [On]

Jari:

The script step you're looking for is:

Set Error Capture [on]

-Stanley

Trying to more accurate, the problem is not entirely within a script. The problem appears when user hits for example Enter-key in FM window, and then doesn't click on the OK-button in the resulting error message window.

When this FM error message is left there, and the external application (which is running in the background) is trying open Filemaker files and the associated scripts within the startup scripts of those files, those scripts won't run even if the Set Error Capture step is there.

So the challenge is how to suppress or ignore program error messages, that are resulting from user hitting keys on the keyboard rather than error messages resulting from particular script steps.

I hope this will explain the problem better.

Jari V