🚀 go-pugleaf

Speed. Variant::OleProperty, Variant::OleFunction (their equivalents) are
great for script languages, but in BCB you can call functions directly.

With TCOM_XXX you call interface functions directly, with
Variant::OleProperty, Variant::OleFunction you make a call through
automation - that is function/property name is converted into id, id into
function pointer, all parameters are converted from Variant to their type -
this takes quite much time, specially if you do this inside cycle. Another
plus is that with TCOM_XXX you will have code completion working.

----------------------------------------------------------------
Regards,
Viatcheslav V. Vassiliev
http://www.oledbdirect.com
The fastest way to access MS SQL Server, MS Jet (MS Access)
and Interbase (through OLEDB) databases.

"Steve_Aletto" <steve_alettoANTI@SPAMhotmail.com> �������/�������� �
�������� ���������: news:3ed22079@newsgroups.borland.com...
> Maybe I'm boring you now but...
>
> Viatcheslav V. Vassiliev <support@oledbdirect.com> wrote in
> message 3ed21b77@newsgroups.borland.com...
> > I mean using ADO is CreateObject(ADODB.xxx) and using
> Access as COM server -
> > CreateObject(Access.xxx), for example,
> CreateObject(Access.Application).
> OK, clear.
>
> > You may have better results with importing ADODB type
> library and using
> > TCOM_Connection, TCOM_Recordset etc. than using Variant
> methods.
> That is my current solution in fact. In what it is better
> than using Variant methods? Speed, size, it's a more
> standard solution, ...?
>
> Steve.
>
>