Database closing problem

[John]

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

 

[rowe_newsgroups]

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

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]

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

 

[Cor Ligthert [MVP]]

Is there a way to ensure that all queries get executed or none?Follow the advice of Seth

Cor

 

[dbahooker]

CORRECTION!

Seth is full of crap
Take your egocentric way of living and shove it up your ass

in ADO classic, we used to be able to open a connection; and close a
connection-- we used to be able to have multiple recordsets on the
same connection

now all we got is bloatware

We used to be able to run ADO commands FROM THE CLIENTSIDE OF THE WEB
BROWSER
this is no longer possible

screw ADO.net





\

 

[dbahooker]

Cor;

stfu and make microsoft fix the BUG

Follow the advice of Seth

Cor

"John" <[email protected]> schreef in bericht




- Show quoted text -

 

[Mark]

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?

Use a proper database?

google: "ado.net transactions"