I have an application that connects to a SQL database across the network. I have error trapping code in place (on error...) but I can't seem to trap the error then network connectivity is lost to the SQL server or there is another problem that prevents connecting to the database. My application opens a connection at startup and leaves the connection open since it's reading/writing data every 2-3 seconds. Is there any way to trap those errors? If so, I could call a routine that tries to reestablish a connection every 'x' seconds instead of failing with an error message. Thanks for any help.