Programmatically get OLDDB Version (and other properties)



Does anyone know how to generically and programatically determine the OLEDB
driver version of an open ADO connection? If this is possible then I would
also like to retrieve other properties about the driver. A list or link to
where I can find this information would be appreciated.

I have scoured Google looking for the answer to what I thought was a simple
problem. I have found some answers that say to check for the following
properties (neither exist):

OLE DB Version
Provider Version

Using a test Oracle connection I retrieved the following list of properties:

Password
Persist Security Info
User ID
Data Source
Window Handle
Locale Identifier
Prompt
Extended Properties
OLE DB Services

I also connected to a test Jet database. It has many more properties and
includes the set of above properties.

TIA,

- Clayton


.



Relevant Pages

  • [bug] stuck localhost TCP connections, v2.6.26-rc3+
    ... That connection has been stuck for 9 ... and it occured on two boxes, both are SMP ... # Bus options ... # Generic Driver Options ...
    (Linux-Kernel)
  • Re: Reading mm datasource
    ... When in Word on my machine, I click on open datasource, pick Connect ... > do not seem to have a specific driver name for the connection string. ... But before you go much further, I hadn't realised you were taking that particular approach to making the connection, and AFAIK the consequence is likely to be that you will be opening your data source, using the "OLE DB Provider for ODBC data sources" which is an approach I know little about but will ...
    (microsoft.public.word.mailmerge.fields)
  • Re: HP JetDirect (now media center and HP 3310)
    ... The problem I am having is not with a HP printer driver. ... In this situation the drive is accessible through Windows Explorer. ... Windows Explorer to force a connection and get Transfer Images to work. ... I am not sure if this will completely work since the setup program may do ...
    (microsoft.public.windowsxp.print_fax)
  • Re: HP JetDirect (now media center and HP 3310)
    ... The problem I am having is not with a HP printer driver. ... In this situation the drive is accessible through Windows Explorer. ... Windows Explorer to force a connection and get Transfer Images to work. ... I am not sure if this will completely work since the setup program may do ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Driver AutoCommit issue
    ... Isn't the XA driver for the distributed transaction, ... the connection pool was getting created. ... When in the code do you do a commit? ...
    (microsoft.public.sqlserver.jdbcdriver)