Is this bad? sqlConnection and command [RESOLVED]

[Andy]

I declared a public SqlConnection and SqlCommand in a module and made it public. I re-use those throughout the life of the app and simply open and close as necessary the connection object and change the command.commandText property as needed. Is that better or worse or the same as going through that process time and time again for each function/sub that may need it?

[nemaroller]

Perfectly fine...

just make sure you check the connection's state property often..

If SqlConnection1.State = ConnectionState.Open Then SqlConnection1.Close

[Andy]

good to know that. i have a routine that checks exactly that and closes it if open. I was worried that my way would not utilize connection pooling correctly and eventually my app would bottleneck.

[hellswraith]

Just use the data application block from MS, then you don't need to do that...

http://msdn.microsoft.com/library/de...ml/daab-rm.asp

[mendhak]

I can personally vouch for the benefits of the DAABs. Intuitive, easy to use, and efficient. And its basically the same thing you're doing in a very generalized fashion.