ExecuteComplete does not fire with adAsyncExecute?

I am using an ADO Command object to execute a stored procedure. I have an
event hander to handle the ExecuteComplete event.

The event handler is called as expected, unless execution is with the
adAsyncExecute option set. In this case, the event handler is not called
upon successful completion execution. (Note: ExecuteComplete is called as
expected if an error is encountered on execution, even if adAsyncExecute is
set.)

In other words, ExecuteComplete does not seem to fire upon successful
completion when the adAsyncExecute option is used.

Am I doing something wrong, or is this an ADO limitation? How am I supposed
to know when asynchronous execution of a stored procedure is complete?
(MDAC 2.8 SP1)

Sincerely,

David Rueter
drueter@xxxxxxxxxx


.

Relevant Pages

  • Window messages
    ... Load event handler set a timer for 200ms and the timer's Tick handler will ... In the execution of the Timer event I use a Process.WaitForExit function to ... window messages when my launcher application was running the timer event. ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Context Menu for ActiveX control in VB.NET
    ... I'm using ActiveX control in my VB.NET project. ... It pops up but execution doesn't stop on Click event handler if I set a break point there. ... Prev by Date: ...
    (microsoft.public.dotnet.framework.windowsforms)
  • Re: Using callback function
    ... If you fire off an event, that event handler gets executed immediately. ... should be able to update the display. ... It get displayed only after the execution of component. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: chooses not to generate code at all
    ... >>>DBMS is so that the DBMS engine can execute it when triggered by some ... If there is no trigger, ... Stored procedure is one thing. ... > If the procedure execution is not triggered by DBMS ...
    (comp.object)
  • Re: Stored Procedures vs DTS vs Jobs
    ... A stored procedure is complied code meaning that SQL Server has already ... > execution time, ...
    (microsoft.public.sqlserver.dts)