>Doggone it, I killed this one months ago and now can't figure out what I did. Try setting the "DispWarnings" SQL property to False.
>
>>
>>>Try SET NOTIFY OFF
>>

DispWarnings will only get rid on non-trappable warnings that come from your ODBC driver. To see an example, make a connection to a Access database through ODBC. Once you connect to get data, you'll get a message (if DispWarnings is .T.) that says something like "can't set asynchronous property" because the Access driver doesn't support it.

Therefore, I wouldn't expect this setting to make much difference.

One thing about this thread: did anyone check or try turning off asynchronous execution? That message is only supposed to appear when the query is actually cancelable (is that a word? <g>) and that's only supposed to be true when the query is running asynchronously.

-Chuck Urwiler, MCSD, MCDBA