Hello,

Has anyone figured out how to have a protocol elegantly quit if and ODBC error (specifically authentication) is thrown?

The current behaviour varies by how the protocol is run:

In webport a standard PP error is given with the "stack trace" and error message

In the pro client the protocol quits as soon as the ODBC connection fails authentication.

I've tried piping the connection to a filter to capture the error but haven't had much success.

Has anyone else dealt with this?

Thanks!