How can I recognize the ADO ExecSQL method finishes in eoAsyncExecute mode?

Hello developmentguru,
Unfortunatelly, OnFetchComplete doesn't occur - at least because the passed guery gives no result. I'm just using one thread, so to have another one is not good way for me, in this case.

Another way could be to use Open method, but it fails with "CommandText does not return a result set". So I tried to set execute options as eoExecuteNoRecords, but then I get "Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another". Do you know why?

I'm attaching to MSSQL Server 2000.
I need to run SQL statement in async mode and display a progress of fetching for each query I enter.

Also, I need to run SQL statement, e.g.:
"SELECT * INTO #tmp FROM table
SELECT * FROM #tmp"
The problem is that in this case the query doesn't fire neither OnFetchProgress nor OnFetchComplete events. Actually, data are fetched so I can display it but, unfortunatelly, I don't know when. In async mode no such event occurs that could inform me about it.

So, I recognized I should separate the qiven SQL into two parts (separated batches):
1. "SELECT * INTO #tmp FROM table" - pure DB side part
2. "SELECT * FROM #tmp" - pure fetching part
Ok, in this case the 2. statement will fire both OnFetchProgress and OnFetchComplete events.

Now, I need to run 1. statement (also in async mode):
The way should be to use ExecSQL method, but it fires (probably?) no event, whereas Open does. Open returns at least AfterOpen event. It is sufficient in this case, because 1. doesn't fetch data.
But as I said before, the Open method fails with "CommandText does not return a result set". So I tried to set execute options as eoExecuteNoRecords, but then I get "Arguments are of the wrong type, are out of acceptable range, or are in conflict with one another".

Perhaps there is need for some "return value" - parameter to be set within ADOQuery???
In SQL Profiler I can see, for 1.:
declare @P1 int
set @P1=1
exec sp_prepexec @P1 output, NULL, N'select * into #tmp from table'
select @P1
What do you think?

Think about my problem as I'm creating something like MS Query Analyzer. Stored procedures are acceptable, but not allways. User would like enter whatever query he wants.When user executes a query, I want to display a progress bar and a cancel button to him.

Everything works ok if the user passes a simple query. If he executes "SELECT * FROM table" it's ok, he can see fetch progress, he is able to cancel the query whenever he wants, etc.
But if user wans to execute "combined" query i.e. something like:
"SELECT * INTO #tmp FROM table
SELECT * FROM #tmp"
- Doesn't matter the query doesn't make sense - it's just an example - I'm not able to catch any event by ADO comps. (Unfortunatelly I have to use ADO; it's a requirement)

A "SELECT 0 result" as you recommended couldn't work, beacuse it is the very same case:
"SELECT * INTO #tmp FROM table
SELECT 0 result"
-it's a "combined" query, so no events. :(

Note:
Following block (i wrote before i have copied this from MS SQL Profiler):
"declare @P1 int
set @P1=1
exec sp_prepexec @P1 output, NULL, N'select * into #tmp from table'
select @P1"
 is a query generated by ADOQuery when I pass "select * into #tmp from table" and ADOQuery.Prepared := True;

===========================
The ideal solution should be to find a way how to catch the events for exactly this query:
"SELECT * INTO #tmp FROM table
SELECT * FROM #tmp"
===========================

Please, test this query and try to find the way.

The strange thing is that if I execute such "combined" query, I can obtain only BeforeOpen event, but no other. Even if data is actually being fetch, I can see with some utility that the data is really being downloaded. But no event raise!!! Why???

Thanks a lot!

Yes, I can understand if it doesn't give me the events for:
"SELECT INTO #tmp",
but if it does for:
"SELECT * from table",
so why it doesn't for:
"SELECT INTO #tmp
SELECT * from #tmp" ???
What's the problem???

Yes, you had! You helped me to stop my hopeless endeavour to find the solution within ADO... :)

I'll separate queries into two parts i.e. ExecSQL and Open.
To be able recognize the first one finishes I'll set ADOQuery ExecuteOptions  := [] while running it "asynchronously" in a thread.
After this I'll run the second part in common "async" way by setting ADOQuery ExecuteOptions  := [eoAsyncExecute, eoAsyncFetch]

I hope this discusion will help also to others;)

Thanks a lot!