Re: ODBC connect string format differs between ODBC driver versions?

"Julian Mehnle, Linksystem Muenchen" wrote:
>
> Hi all!
>
> I have an Access 2000 database (under Windows 2000) which has tables linked
> from a PostgreSQL database. These tables have been linked using the
> PostgreSQL ODBC driver 7.01.0004 or some version around that (sorry, I don't
> remember the exact version). The Access ODBC connect string of one table is:
>
> ODBC;DSN=lmdb;DATABASE=lmdb;SERVER=sphinx.link-m.de;PORT=5432;
> UID=lmdb;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=0;SHOWOIDCOLUMN=0;
> ROWVERSIONING=1;SHOWSYSTEMTABLES=0;CONNSETTINGS=;TABLE=**Logfile
>
> However, I have now installed a newer version of the ODBC driver
> (7.01.0009), and when I create a new table link for the *same* table, I get
> quite a different ODBC connect string:
>
> ODBC;DSN=lmdb;DATABASE=lmdb;SERVER=sphinx.link-m.de;PORT=5432;
> A0=0;A1=6.4;A2=0;A3=0;A4=1;A5=0;A6=;A7=100;A8=4096;A9=0;B0=254;
> B1=8190;B2=0;B3=0;B4=1;B5=1;B6=0;B7=1;B8=0;B9=0;C0=0;C1=0;
> C2=dd_;;TABLE=**Logfile
>
> Questions:
>
> * Did the ODBC connect string format indeed change between ODBC driver
> versions?

Yes it was changed in 7.01.0007. Most driver options are changed
to be DSN options.

> * Can I still use the old format with newer ODBC drivers without having to
> expect any disadvantages or bugs?

Unfortunately I couldn't guarantee that the change was
bug-free. However I have seen no bug report other than
implicit *too long connect string* bug. A0=,B1= etc are
abbreviated format to shorten connect strings. Original
format READONLY= etc is still allowed.

regards,
Hiroshi Inoue