🚀 go-pugleaf

Info literals and keywords are really not defined in OLEDB as schema - OLEDB
provider provides this information not through schema mechanism and ADO
transforms this to schema. If you need more info, look MDAC SDK or MSDN.

----------------------------------------------------------------
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.


"Edward Diener" <eddielee@tropicsoft.com> �������/�������� � ��������
���������: news:3ead97a6@newsgroups.borland.com...
> Viatcheslav V. Vassiliev wrote:
> > ADO Express (dbGo) uses MS ADO to get schema data, so it supports any
> > schema that ADO supports. adSchemaDBInfoLiterals is defined in ADO
> > but not in OLEDB - OLEDB providers provide this information not
> > through schema.
>
> Why then does the Borland doc quoted below say that
>
> "siDBInfoLiterals (Defined in OLE DB, but not supported by ADO.)"
>
> along with a number of other siXXX schema types ( look at the bottom of
the
> TSchemaInfo type topic ) ? Is this just another error by Borland in their
> documentation ?
>
> >
> > ----------------------------------------------------------------
> > 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.
> >
> >
> > "Edward Diener" <eddielee@tropicsoft.com> �������/�������� � ��������
> > ���������: news:3eabd2f1$1@newsgroups.borland.com...
> >> The documentation for OpenSchema's TSchemaInfo types says that says:
> >>
> >> "siDBInfoLiterals (Defined in OLE DB, but not supported by ADO.)"
> >>
> >> among other types specified as defined in OLEDB but not ADO. However,
> >> looking at the MS ADO documentation, it clearly states that
> >> adSchemaDBInfoLiterals, the ADO equivalent of siDBInfoLiterals, is
> >> supported in ADO. Does anybody know why Borland's ADO implementation
> >> says that it is not supported ? Is the Borland ADO implementation a
> >> version of ADO that is not the latest and does not support this
> >> functionality ? I notice the latest version of ADO on my machine is
> >> 2.7, which I guess corresponds to the 2.7 version of MDAC. What
> >> version of ADO does Borland's version support ?
>
>