Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Process object does not go out of scope
Message
From
01/04/2008 04:01:19
 
 
To
31/03/2008 14:26:58
General information
Forum:
ASP.NET
Category:
Other
Environment versions
Environment:
VB 8.0
OS:
Windows XP SP2
Database:
Visual FoxPro
Miscellaneous
Thread ID:
01306828
Message ID:
01307252
Views:
7
>>In VB it should be simply something like:
>>Using oConn As New Connection(.....)
>>  ' Execute your SQL statement
>>End Using
>>The connection should be automatically disposed when code leaves the 'Using' scope.
>
>For each hit, we do from 10 to 20 SQL commands on average. So, I cannot use this approach.

Why not? Open, Execute, Close. Do it however many times are required. I don't think you will find the overhead to be as high as you fear.
Regards,
Viv

This is why I open the connection at the BeginRequest() method and close it in EndRequest().
>
>>This was using the VFPOLEDB? In that case I'm afraid, top of my head, I don't know.....
>
>Ok
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform