Re: other language descriptions for microsoft ODBC drivers
- From: Bob Hairgrove <NoSpamPlease@xxxxxxxx>
- Date: Thu, 05 Jul 2007 09:47:56 +0200
On Wed, 04 Jul 2007 11:45:47 +0200, Bob Hairgrove
<NoSpamPlease@xxxxxxxx> wrote:
(c) When the user selects one of the drivers and creates a DSN,
establish a connection to this (if possible) and call SQLGetInfo on
the connection handle, passing SQL_DRIVER_HLIB as an argument. This
will return the name of the DLL used to implement the current driver.
Oops ... I left out one step ... you receive an instance handle of
the DLL from SQLGetInfo() which you can use to call the Win32 API
function GetModuleName(), and THAT you can compare with your list of
supported DLLs.
Sorry for the confusion.
--
Bob Hairgrove
NoSpamPlease@xxxxxxxx
.
- Follow-Ups:
- Re: other language descriptions for microsoft ODBC drivers
- From: cshashikanth
- Re: other language descriptions for microsoft ODBC drivers
- References:
- other language descriptions for microsoft ODBC drivers
- From: cshashikanth
- Re: other language descriptions for microsoft ODBC drivers
- From: Bob Hairgrove
- Re: other language descriptions for microsoft ODBC drivers
- From: cshashikanth
- Re: other language descriptions for microsoft ODBC drivers
- From: Bob Hairgrove
- Re: other language descriptions for microsoft ODBC drivers
- From: Bob Hairgrove
- Re: other language descriptions for microsoft ODBC drivers
- From: Bob Hairgrove
- other language descriptions for microsoft ODBC drivers
- Prev by Date: Re: other language descriptions for microsoft ODBC drivers
- Next by Date: Re: Very long to to insert a row in an Oracle linked server
- Previous by thread: Re: other language descriptions for microsoft ODBC drivers
- Next by thread: Re: other language descriptions for microsoft ODBC drivers
- Index(es):
Relevant Pages
|
|