CPGDeveloper
Board Regular
- Joined
- Oct 8, 2008
- Messages
- 190
Hello ~
I administer an MS Access DB Application (MS Access FE/Azure SQL Server Back End).
My end users are occasionally receiving ODBC Connection errors -- they seem to be relatively rare and random, but I would like to capture them and spit out a clean error message instead of the long message spit out by SQL Server.
I have error handlers throughout my code, however, 'On Error' does not seem to capture these errors. Everything else I've read online provides advice on what to do after I've captured the error, but I can't seem to figure out how to capture it in the first place. Any advice would be greatly appreciated.
Thanks.
I administer an MS Access DB Application (MS Access FE/Azure SQL Server Back End).
My end users are occasionally receiving ODBC Connection errors -- they seem to be relatively rare and random, but I would like to capture them and spit out a clean error message instead of the long message spit out by SQL Server.
I have error handlers throughout my code, however, 'On Error' does not seem to capture these errors. Everything else I've read online provides advice on what to do after I've captured the error, but I can't seem to figure out how to capture it in the first place. Any advice would be greatly appreciated.
Thanks.
