Re: Problem with AsyncExecute in ADO
- From: "Steve Zimmelman" <skz@xxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Aug 2006 17:21:01 -0500
When you execute asynchronously it processes the code after the "open" before
the "open" is complete. If execute in Synchronous mode, the process will wait
for the "open" to complete before moving to the next line of code.
-Steve-
"Mat Datasym" <matt@xxxxxxxxxxxxx> wrote in message
news:44f5dcec$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the response, but sorry, I don't understand your response. Surely
after executing asynchronously the recordset should still be open.
When I interrogate the status after execution has completed the status is
closed. This can't be right!!
.
- References:
- Re: Problem with AsyncExecute in ADO
- From: Vitali Kalinin
- Re: Problem with AsyncExecute in ADO
- From: Mat Datasym
- Re: Problem with AsyncExecute in ADO
- Prev by Date: Re: Problem with AsyncExecute in ADO
- Next by Date: Re: Outer join in Access
- Previous by thread: Re: Problem with AsyncExecute in ADO
- Next by thread: TDBmemo fields and Memory Tables
- Index(es):