Re: Delphi 6 - ADO - MS SQL Server
- From: angus@xxxxxxxxxxxx (Angus Robertson - Magenta Systems Ltd)
- Date: Fri, 22 Sep 2006 17:17 +0100 (BST)
In article <451404c5$1@xxxxxxxxxxxxxxxxxxxxxx>, gnome@xxxxxxxxx
(AquaGrrlll) wrote:
When I set up the thread I give it it's own TADOConnection as well
as the TADOStoredProc:
Why are you using a thread? You can drive the whole thing with events,
the first event is when the connection to SQL is made, that triggers the
Execute EXEC statements, and ExecuteComplete then triggers any more
Exectutes, until you've finished. This is none blocking, and you can
have several connections to different databases running at the same
time, no threads.
Problem is, that isn't happening. OnExecuteComplete never fires and
the whole thing hangs.
I don't use TADOStoredProc, I just Execute on the connection, checking
Recordset in the event for success. The simpler, the safer.
I'm using these techniques to capture records arriving by multiple TCP
and UDP streams to different database tables, up to 50 records per
second, all in a single thread.
Angus
.
- References:
- Re: Delphi 6 - ADO - MS SQL Server
- From: AquaGrrlll
- Re: Delphi 6 - ADO - MS SQL Server
- Prev by Date: Re: Delphi 6 - ADO - MS SQL Server
- Next by Date: Trouble with TADOQuery
- Previous by thread: Re: Delphi 6 - ADO - MS SQL Server
- Next by thread: Re: Delphi 6 - ADO - MS SQL Server
- Index(es):
Relevant Pages
|