title: maintain one ODBC connection or connect/dispose each use?
body: <p>In my application, I have a function that executes SQL lines that can be called several hundreds of times depending on what the user decides to do.  Would it be better to have the application open a connection at the start and re-use that connection throughout the user session to execute commands as they are needed or to have the function open the connection, execute the SQL line, and close the connection each time a procedure needs to be executed?  </p>
  
  <p>Sorry if this is a pretty basic or general question - just curious if there's a "best practice".</p>
  
  <p>Thanks!</p>
  
  <p>Randy</p>