Connection String

[Jagjit]

Hi

I want to make a connection string & it should try to make connection in a certain period of time . If connection successful them o.k else it give message "timeout,unable to make connection within specified time"

Thanks

[dilettante]

ADO Connection objects can be declared WithEvents.

Then you can call the Open method passing adAsyncConnect, and Enable a Timer control.

If the Timer fires before the Connection raises its ConnectComplete event you can call the Cancel method.


All of this is covered in the MSDN Library CDs that shipped with legal copies of VB6.

[Jagjit]

Hi

Isn't there any option of timeout in connection string

Thanks

[jmsrickland]

ADO Connection objects can be declared WithEvents.

Then you can call the Open method passing adAsyncConnect, and Enable a Timer control.

If the Timer fires before the Connection raises its ConnectComplete event you can call the Cancel method.


All of this is covered in the MSDN Library CDs that shipped with legal copies of VB6.

How do you know it has to do with ADO when that is not even mentioned

[DataMiser]

How do you know it has to do with ADO when that is not even mentioned

The term "Connection String" is a pretty good hint. That and being in a VB6 forum.

[jmsrickland]

Oh, OK. I don't know ADO so that's why I asked

[techgnome]

ADO Connection objects can be declared WithEvents.

Then you can call the Open method passing adAsyncConnect, and Enable a Timer control.

If the Timer fires before the Connection raises its ConnectComplete event you can call the Cancel method.


All of this is covered in the MSDN Library CDs that shipped with legal copies of VB6.

Hi

Isn't there any option of timeout in connection string

Thanks

Or... you just create the connection object, set the connectionstring, set the ConnectionTimeout property, wrap it in an error handler, and then attempt to open it. If it doesn't open within the time specified by the CommandTimeout, and error will be raised... if the connection is successful, then it opens, and the code continues.

-tg

[dilettante]

True enough, though as it says in the manual:

Make sure the provider to which you are writing code supports the ConnectionTimeout functionality.

Then if the interval is short enough (5 seconds or less) hanging on a synchronous Open works too. Longer than that and Windows will mark you "unresponsive" (irresponsible?). Plus you have no way to let the user "cancel" a connection attempt that takes too long.