Re: ado.connected:=false fails
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 12/23/04
- Previous message: Brian Bushay TeamB: "Re: problem with Timeout Expired""
- In reply to: Jozza: "Re: ado.connected:=false fails"
- Next in thread: Jozza: "Re: ado.connected:=false fails"
- Reply: Jozza: "Re: ado.connected:=false fails"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 22 Dec 2004 17:17:37 -0600
>Setting the connectionobject to nil has no effect in any case. it is always
>pointer($...) as _connection.
It has an effect in my code.
>I know now that this happens when i call execute from another thread than
>the main thread and execute fails.
>I tried to call execute from the main thread which failed, and then setting
>connected to false and it worked.
>After execute fails from another thread, it is not possible to set
>ado.connected:=false anymore. What can be the cause for that? the driver is
If you are executing from another thread then you should be creating a second
TadoCommand object and you need to close that instance.
>ibm db2 and provider is msdasql.
I can't help you with db2 specific problems. If you can reproduce it with SQL
server I may be able to help
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Previous message: Brian Bushay TeamB: "Re: problem with Timeout Expired""
- In reply to: Jozza: "Re: ado.connected:=false fails"
- Next in thread: Jozza: "Re: ado.connected:=false fails"
- Reply: Jozza: "Re: ado.connected:=false fails"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]