Re: SQORA.DLL doesn't recognize DBQ parameter?
Date: Thu, 27 Oct 1994 17:20:09 GMT
Message-ID: <James.Lawrence.18.000C565F_at_epamail.epa.gov>
In article <wmeahan.211.00084455_at_ef0424.efhd.ford.com> wmeahan_at_ef0424.efhd.ford.com (Bill Meahan) writes:
>From: wmeahan_at_ef0424.efhd.ford.com (Bill Meahan)
>Subject: SQORA.DLL doesn't recognize DBQ parameter?
>Date: Thu, 20 Oct 1994 08:15:57
>Keywords: ODBC Oracle
> According to the documentation for the SQORA.DLL (Page Ahead
> ODBC driver for Oracle Version 6, distributed by Microsoft)
> one should be able to pass a parameter named DBQ as part of an
> ODBC connect string. DBQ should contain an Oracle "network
> connect string" as used by SQL*Net and it is implied that this
> will override the "Server=" entry in the ODBC.INI file.
>
> In fact, this does not work: connection is made to whatever
> server/instance is specified by the "Server=" line of the
> ODBC.INI file regardless of what is passed via the DBQ parameter.
> Lack of a "Server=" line or no SQL*Net connection string on the
> "Server=" line results in an ORA-9301 error.
>
> We are up to date on the SQORA.DLL version (....3112).
>
> Any fixes/workarounds? This is a showstopper for an application
> being developed here and the cost of buying an ODBC driver (e.g.
>Intersolv/Q+E at $99/seat) would be prohibitive.
Change the entry in the ODBC file on the fly from your app before doing the connect.
>
>And no, moving to Oracle 7 is not currently an option :-)
>--
>Bill Meahan, Senior Developer | wmeahan_at_ef0424.efhd.ford.com
>Electrical & Fuel Handling Division, Ford Motor Company
> "Computers are the most stupid machines in the world -
> they do EXACTLY what you TELL them to do!" (Gus Ogletree)
Received on Thu Oct 27 1994 - 18:20:09 CET