problem with latest stable driver

problem with latest stable driver

am 31.03.2006 13:47:58 von me

This is a multi-part message in MIME format.

------=_NextPart_000_037F_01C654C9.B857A870
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

hi list

probably an old problem, but i wasn't able to follow the list for a =
while. after we upgraded the odbc version to the latest driver (pgsql: =
8.1.3 with odbc: 8.1.2), all unicode TEXT-output was totaly messed up. i =
wasn't able to find any changelogs descripting changes from the 8.1.1 =
(where everything works just fine) to 8.1.2 (where ADODB output of TEXT =
is totaly messed up on our win2k3 system).=20

this is probably a known problem by now, but as i wasn't able to find =
any link to a newer dev-version on pgfoundry, i wanted to ask here what =
the best steps are to avoid this (aside from downgrading to driver v. =
8.1.1)

thanks,
thomas
------=_NextPart_000_037F_01C654C9.B857A870
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable



charset=3Diso-8859-1">




hi list

 

probably an old problem, but i wasn't =
able to=20
follow the list for a while. after we upgraded the odbc version to the =
latest=20
driver (pgsql: 8.1.3 with odbc: 8.1.2), all unicode TEXT-output was =
totaly=20
messed up. i wasn't able to find any changelogs descripting changes from =

the 8.1.1 (where everything works just fine) to 8.1.2 (where ADODB =
output=20
of TEXT is totaly messed up on our win2k3 system).

 

this is probably a known problem by =
now, but as i=20
wasn't able to find any link to a newer dev-version on pgfoundry, i =
wanted to=20
ask here what the best steps are to avoid this (aside from downgrading =
to driver=20
v. 8.1.1)

 

thanks,

thomas


------=_NextPart_000_037F_01C654C9.B857A870--