Can you post the relevant code?

Without seeing the code is hard to tell, just make sure you always close the connection and set the object to nothing before exiting the application. It could also be a timeout problem, for that you can try increasing the connection timeout value.

>I was wondering if anyone else has seen a problem like mine.
>
>I have an application, written in Sql Windows, that calls a list of other applications (exes) that are mostly written in Sql Windows. I have created three VB Apps that run towards the end of this list. So when each app is finished, they send a message back to the main app telling it that it is finished, so the main app, in turn, calls the next one in the list. So anyway, my first 30+ apps that are written in Sql Windows, work fine. I get to the first VB App, it connects to the Oracle database using ADO, and it always connects just fine. The next app is Sql Windows, works fine, then my next two apps, which are written in VB, sometimes connect and sometimes don't. They alternate on which one wants to connect. Typically, if the second VB app doesn't connect, the third one will. Sometimes the second connects fine and the third one won't. In all three apps I use the same exact way to connect. My connection code is in a module that all three apps include to make my database connections. I
>even set up error trapping to try to connect 30 times with a second delay in between if it fails. Sometimes, like once a week, all three connect fine. But for the most part, at least one of the last two don't connect. Every time I have run all three apps by themselves, I have no problems at all. Does anyone have any ideas on what is going on?
>
>Thanks for your help.