July 20, 2010 at 3:00 pm
Check your code may be in test mode it is closing connection to the database after certain point. In VB once the connection is open it will remain open until you explicitly close.
SKC
July 21, 2010 at 2:55 am
Sounds like a possible scenario is this:
The app just used to open connections and leave them open for multiple screens/processes or whatever. You have now corrected this by closing them connections between database operations, but the app is still making assumptions that the connection is open.
Quite often VB6 apps I have come across use a global variable to represent a SQL connection, which is closed and set to nothing after a database operation. If you try and use the connection without setting it to a new ADODB.Connection and opening that connection that could cause the issue.
July 22, 2010 at 3:00 am
Debug the code - and the problem should be evident.
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply