Received: from rm-rstar.sfu.ca (root@rm-rstar.sfu.ca [142.58.120.21]) by hub.org (8.9.3/8.9.3) with ESMTP id QAA34079 for ; Wed, 1 Sep 1999 16:32:38 -0400 (EDT) (envelope-from blackw@rm-rstar.sfu.ca) Received: from cultus.sfu.ca (cultus.sfu.ca [142.58.200.80]) by rm-rstar.sfu.ca (8.9.2/8.9.2/SFU-5.0H) with ESMTP id NAA14480 for ; Wed, 1 Sep 1999 13:32:37 -0700 (PDT) Message-Id: <199909012032.NAA14480@rm-rstar.sfu.ca> Content-Type: text/plain Content-Disposition: inline To: pgsql-interfaces@postgresql.org From: blackw@sfu.ca Mime-Version: 1.0 Reply-To: blackw@sfu.ca Date: Wed, 01 Sep 1999 20:32:37 GMT X-Mailer: SFUwebmail 2.70 Subject: Re: [INTERFACES] odbc V3+ Paul wrote: > Any scuttle butt on when the Postgresql odbc will move from 2 to 3? To which Byron replied: > Not very likely. [SNIP-O-RAMA] The driver > should still work with odbc 3.0 applications because the odbc driver > manager is supposed to convert calls to odbc 2.x on the fly. I'm not > sure how extensively it does this. I'd like to know where you came across this information, as I have not been able to confirm anywhere that a driver manager will perform the conversion you suggest. Quite to the contrary, I have found the following statement in Microsoft documentation: "Applications that follow the ODBC 3.x specification must use conditional code to avoid using functionality new to ODBC 3.x when working with ODBC 2.x drivers. ODBC 2.x drivers do not support functionality new to ODBC 3.x just because the application declares that it follows the ODBC 3.x specification." (MSDN Library - April 1999/ Platform SDK/ Data Access Services/ Microsoft Data Access 2.1 SDK/ Microsoft Open Database Connectivity (ODBC)/ Part 2 Developing Applications and Drivers/ Chapeter 6: Connecting to a Data Source or Driver/ Page: Delcaring the Application's ODBC Version ) So, if you have a resource that indicates the contrary, I'd sure like to get my hands on it. Thanks. Cheers, Richard Blackwell Programmer/Analyst Dept. of Psychology, Simon Fraser University Burnaby, BC Canada