Groups | Blog | Home
all groups > dotnet ado.net > may 2007 >

dotnet ado.net : Database closing problem


rowe_newsgroups
5/3/2007 9:46:54 AM
[quoted text, click to view]

I'm guessing you are trying to use a global connection object right?

If so, change the code to open a connection to the database, execute
your commands, and then close/dispose of the command and connection.
You should try to avoid using a "global" connection object at all
costs as it can lead to serious problems (with very few benefits). If
I guessed wrong, please post your code so I can take a look.

Thanks,

Seth Rowe

John
5/3/2007 4:55:32 PM
Hi

I have a vb.net app that opens an access database runs several sql action
queries on the tables and closes the db. This is done every few minutes. The
problem is that sometimes I get an error 'ExecuteNonQuery requires an open
and available Connection. The connection's current state is closed'. My
question is; is there a situation where an app automatically closes the db
connection causing this error and is there a way to prevent this?

Thanks

Regards

John
5/3/2007 6:53:27 PM
Hi Seth

It is true that I am opening a global connection. Executing only some of sql
queries will cause problem with the integrity of the data in the database.
By using a global connection I was hoping to provide a guaranteed connection
to all queries reducing any expected problems. Is there a way to ensure that
all queries get executed or none?

Thanks

Regards

[quoted text, click to view]

Cor Ligthert [MVP]
5/4/2007 12:00:00 AM
[quoted text, click to view]
Follow the advice of Seth

Cor

"John" <John@nospam.infovis.co.uk> schreef in bericht
news:uaP11vajHHA.3120@TK2MSFTNGP05.phx.gbl...
[quoted text, click to view]

AddThis Social Bookmark Button