When writing apps with asp.net, which I do more of than vb.net apps, I have always followed the rule of opening a connection to the server, getting the data, and closing the connection as quickly as possible. This seems like a best practice.
Is it equally important to do this on a client/server vb.net app? For example, if you had multiple forms, each either with a grid of data, or a form of data, would you typically open the connection when each form started, close it when the user left the form? or is it acceptable to define a global variable for the connection and keep it open the entire life span of the app?
Personally I would tend to open/close the connection with each form, but wondering what other folks recommend with a typical desktop c/s app?
Only use it when you need it. Don’t keep things lying around if you’re not going to need it and use it right away. Same principle of declaring your variables and using them soon, rather than, say, having an enormous list of declarations near the top and using them later – this is confusing and can leave things unused unnecessarily.
Also, if you stick with the using statement pattern whenever you’re using your SQL connection then it will do the closing for you. This is better than having it scattered and potentially forgetting to close it – depending on load this could tie up your connections and eventually lead to some connections being refused. I’m not saying you’re not already doing this, but just in case. Most MSDN examples will show the using pattern for classes that implement IDisposable.
More on using here. The SqlConnection example shows the same thing. The using statement has the added benefit of acting like a try/finally block.