Glad you were able to solve this. I had a situation that was somewhat similar a while back. I also employed a work-around like you are describing to handle the problem.


>>How are you updating the table structures. Do you use Stonefield Database Toolkit or something equivalent?
>>
>>Possibly the answer would be to get the structure correct before opening the form?
>
>Stacy,
>
>Thanks for the response.
>
>The updating isn't the problem. I'm already using SDT to handle data structure updates. However, I have no control over a client restoring an older data set to do testing. It's a weird situation, because the problem is clearly caused by them, but the interactive error was causing their batch scheduler to hang.
>
>I did find a workaround through the form's Error event. First, I check to see if we're running the form through our command line utility (via Application.ServerName). If so, I log the error and exit the process completely. Otherwise, I just pass the error back out via the ERROR statement. This solution prevents the interactive error dialog from popping up.
>
>Laterness,
>Jon