VBA error trapping for SQL Server connection (1 Viewer)

Hello!

I have a front end Access DB 2007 that calls stored procedures (SP) in SQL Server 2010 (ODBC connection through DSN). Today the server went down while a SP was executing. The Access application just hung and could not be closed by any other means than through task manager.

How do I trap a connection error like this?


Thanks,

Johan

Does it have any On Error (Error handling code) statement?
Here's the error numbers that typically occur when there's a loss of network connectivity:
3024, 3044, 3043, 3078

IAccess said:

Today the server went down while a SP was executing.

Click to expand...

Access / VBA called the SP, and WHILE the SP was executing the server went down, never to return? Ugly situation...

I have no experience with LONG running SP's, even SP's many printed pages long execute in the blink of an eye.

So are you using ADO objects to execute the SP, DAO objects, or or or...

I am thankful,