🚀 go-pugleaf

Viatcheslav,
    I think I understand the different values which the ExecuteOptions can
be set to. What I don't understand is how to actually ASSIGN them to the
ExecuteOptions property! I have tried all of the following statement
structures:

1.)
qry->ExecuteOptions << eoAsyncExecute     // works for other set-style
properties in Borland
2.)
qry->ExecuteOptions = qry->ExecuteOptions << eoAsyncExecute     // your tip
3.)
TExecuteOptions eo;
eo << eoAsyncExecute;     // if I inspect eo, it DOES actually contain
eoAsyncExecute at this point
qry->ExecuteOptions = eo;     // woops, where did it go?

Each attempt always yields the same result: the ExecuteOptions property
seems to be empty (contains the null byte, "\0"). I'm almost convinced this
has to be a bug, because I CAN modify the ExecuteOptions property of a
TADOCommand object. Any ideas how I could confirm or dispel this with
Borland? At any rate, thanks for your response.

-Mike

"Vassiliev V.V." <news@vassilievvv.mtu-net.ru> wrote in message
news:3df86103@newsgroups.borland.com...
> Try use eoExecuteNoRecords for SQL statements that do not return recordset
> such as delete statement. Also
>
> qry->ExecuteOptions = qry->ExecuteOptions << eoAsyncExecute
>
> can help.
>
> ----------------------------------------------------------------
> Regards,
> Viatcheslav V. Vassiliev
> http://www.oledbdirect.com
> The fastest way to access MS SQL Server, MS Jet (MS Access)
> and Interbase (LCPI provider, http://www.lcpi.lipetsk.ru) databases.
>
> "Mike Skelton" <MSkelton@vrms.com> �������/�������� � �������� ���������:
> news:3df7b98a$1@newsgroups.borland.com...
> > Hello everyone,
> >     I'm having difficulty setting the ExecuteOptions property of a
> TADOQuery
> > object. Is this a known bug or is anyone else experiencing the same
> problem?
> > What I'm trying to accomplish is the execution of an SQL delete
statement
> > asynchronously on a database server. I've toyed around with the
> > CursorLocation, CursorType, and various other properties to see if I
need
> a
> > certain combination, but to no avail. Each time I attempt to set the
> > ExecuteOptions property (using the << operator for the Set container,
for
> > example, "qry->ExecuteOptions << eoAsyncExecute"), I simply get "\0" as
a
> > value. What gives!?! I'm able to use different ExecuteOptions with
> instances
> > of TADOConnection and TADOCommand objects, however TADOQuery doesn't
seem
> to
> > respond to modifying this property.  My data provider is MSDASQL. If
> anyone
> > can confirm this as a bug or tell me what I'm doing wrong, I'd really
> > appreciate it.
> >
> > Thanks
> > -Mike
> >
> >
>
>