By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
448,784 Members | 1,205 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 448,784 IT Pros & Developers. It's quick & easy.

Database closing problem

P: n/a
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
May 3 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
On May 3, 11:55 am, "John" <J...@nospam.infovis.co.ukwrote:
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
May 3 '07 #2

P: n/a
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

"rowe_newsgroups" <ro********@yahoo.comwrote in message
news:11*********************@l77g2000hsb.googlegro ups.com...
On May 3, 11:55 am, "John" <J...@nospam.infovis.co.ukwrote:
>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


May 3 '07 #3

P: n/a
Is there a way to ensure that all queries get executed or none?
>
Follow the advice of Seth

Cor

"John" <Jo**@nospam.infovis.co.ukschreef in bericht
news:ua**************@TK2MSFTNGP05.phx.gbl...
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

"rowe_newsgroups" <ro********@yahoo.comwrote in message
news:11*********************@l77g2000hsb.googlegro ups.com...
>On May 3, 11:55 am, "John" <J...@nospam.infovis.co.ukwrote:
>>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



May 4 '07 #4

P: n/a
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

\
On May 3, 9:46 am, rowe_newsgroups <rowe_em...@yahoo.comwrote:
On May 3, 11:55 am, "John" <J...@nospam.infovis.co.ukwrote:
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

May 4 '07 #5

P: n/a
Cor;

stfu and make microsoft fix the BUG


On May 3, 10:28 pm, "Cor Ligthert [MVP]" <notmyfirstn...@planet.nl>
wrote:
Is there a way to ensure that all queries get executed or none?

Follow the advice of Seth

Cor

"John" <J...@nospam.infovis.co.ukschreef in berichtnews:ua**************@TK2MSFTNGP05.phx.gbl. ..
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
"rowe_newsgroups" <rowe_em...@yahoo.comwrote in message
news:11*********************@l77g2000hsb.googlegro ups.com...
On May 3, 11:55 am, "John" <J...@nospam.infovis.co.ukwrote:
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- Hide quoted text -

- Show quoted text -

May 4 '07 #6

P: n/a
On Thu, 3 May 2007 18:53:27 +0100, "John" <Jo**@nospam.infovis.co.uk>
wrote:
>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"
May 13 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.