Environment versions
Network:
Windows 2008 Server
>>Personally I prefer to establish connections on demand which helps a great deal.
>>
>>This may not be practical in situations where your application is rapidly firing off queries or commands that can't be neatly grouped into a batch (where you connect before and disconnect afterward). In that case, it is helpful to wrap the SQLEXEC command in a class that checks the connection state before sending the command. Sending simple command like Select GetDate() will reveal if the connection is functional. If not, reconnect.
>
>Actually, the simplest one I know of is
>
>sqlexec(h, "")
It is useless.
You can lose the connection after a ns result SQLEXEC (h, "").
The only way it is to send the true command and check the result.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only