I thought I had that in place, but maybe I missed some spots. I'll double check and let you know. Thanks.
Main Topics
Browse All TopicsI 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.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: ketapillarPosted on 2003-11-11 at 14:10:23ID: 9726210
try adding this before you execute the sql...
If ConnSQL.State <> adStateOpen Then ConnSQL.Open
where ConnSQL is the name of your connection