Mark,
I think many of us use SET ASSERT to help debug, rather than as a mini-error handler. EVERY distributed app. should have a robust error handler to take care of the inevitable bugs, but SET ASSERT isn't the right tool for this.

Barbara

>Actually, I agree. SET ASSERT should be off, only because if an error can happen during development, it can happen at the end-user's desk (though there are probably a few exceptions). Therefore, the error should be trapped like any other error, rather than risk corrupting data.
>
>By catching errors with assertions, and turning that checking off for the final product, you are saying your code contains no bugs that those assertions trapped, aren't you? Either that, or you'll take that chance over the speed hit.