🚀 go-pugleaf

Thomas,

Thanks for the trick, it does work.

I posted the original thread for two weeks without a response, I thought I
should fix the bug myself. I went through the ADO source code and found that
the ADOQuery & ADOStoredProcedure have their own Timeout parameters which do
relate to the Timeout parameter of the ADOConnection at all - same as what
you said.

I have then created a derived class of ADOQuery and ADOStoredProcedure, with
these derived classes I can now control the timeout parameter. If you need
the source for the derived, let me know.

Peter



Thomas Wagener <wagener@rs-system.de> wrote in message
news:3add6123_2@dnews...
>
> "Peter Dam" <pdam@tesco.net> schrieb im Newsbeitrag
news:3ac8a67e_1@dnews...
> > Hi I am not sure if anyone has this problem before.
> >
> > I updated the ADO component recently, and have found that the new ADO
> > component ignores the values set in Command and Connection Timeout
> > parameters, and always generates a timeout error message after 30
seconds.
> >
> > This means that I cannot run any query which takes longer than 30
seconds.
> >
> > I wonder is there any solution to this problem? I am using BCB5
Enterprise
> > version, and the latest ADO component downloaded from Borland web site.
> >
> > Thanks in advance
> >
> > Peter
>
> Hi Peter,
>
> I had the same problem but yesterday I found a solution that works for me
on
> the Borland community site. The solution was well hidden in some chat
> transcript.
>
> My problem was that the ConnectionTimeout property of TADOConnection had
no
> effect when I use the TADOConnection instance with a TADOQuery object. The
> ConnectionTimeout property of TADOQuery is read-only. For this reason you
> are stuck with TADOQuery.
> The workaround is to use a TADODataSet.
>
> So, instead of
>
>     dbConnectionPtr= new TADOConnection(0);
>     dbConnectionPtr->ConnectionString = connectionString;
>     dbConnectionPtr->ConnectionTimeout = 120; // Set timeout to 120 s.
>     dbConnectionPtr->Open(userName,passWord);
> ...
>         TADOQuery* dbFileQuery = new TADOQuery(0);
>         dbFileQuery->Connection = dbConnectionPtr;
>         dbFileQuery->SQL->Text = queryString;
>         dbFileQuery->Open();
> ...
> // ConnectionTimeout has NO effect
>
> you should use
>
>         TADODataSet* dbDocumentQuery = new TADODataSet(0);
>             dbDocumentQuery->Connection = dbConnectionPtr;
>             dbDocumentQuery->CommandTimeout=300;
>             dbDocumentQuery->CommandType = cmdText;
>             dbDocumentQuery->CommandText = queryString;
>             dbDocumentQuery->Open();
>
> // Timeout is set to 300s.
>
> Hope this helps,
>
> Thomas
>
>