|
-
Feb 15th, 2006, 01:42 PM
#1
Thread Starter
Addicted Member
ADO with SQL Server 2000
Background info: I have a VB6 application where I am going to convert it from writing to an Access database to a SQL Server DB instead. I have a stored procedure for inserting records that I was hoping to use.
Problem: In ADO.net it is easy to open your connection, call your stored procedure then close the connection. It seems like all the example code for ADO that I find ends up leaving the connection open the whole time the application is running.
Question: Is there anything wrong with opening and closing my connection each time I call the stored procedure using ADO?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|