Обсуждение: ODBC 09.03.0100 - Issue with new-line-conversion
Hi Hiroshi, is there an issue with new-line-conversion in the new ODBC 09.03.0100 ? I've got an PG 9.3 64bit server on Linux. The clients are Win XP or 7 with MS-Access 2003 or 2010. All ODBC are 32 bit. I've got the new-line-conversion as parameter in the connection string as PG uses only LF and Access needs CRLF. Up until V09.02.0100 the on the fly conversion works. With 09.03.0100 the line breaks in text fields get lost when displayd in Access. Is there a changed parameter or is there a bug in the new ODBC? Regards Andreas
On 02/20/2014 08:26 AM, Andreas wrote: > Hi Hiroshi, > > is there an issue with new-line-conversion in the new ODBC 09.03.0100 ? > > I've got an PG 9.3 64bit server on Linux. > The clients are Win XP or 7 with MS-Access 2003 or 2010. > All ODBC are 32 bit. > > I've got the new-line-conversion as parameter in the connection string > as PG uses only LF and Access needs CRLF. > Up until V09.02.0100 the on the fly conversion works. > > With 09.03.0100 the line breaks in text fields get lost when displayd in > Access. > > Is there a changed parameter or is there a bug in the new ODBC? Yes. See this thread: http://www.postgresql.org/message-id/006a01cf28e4$7c425450$74c6fcf0$@de In particular: http://www.postgresql.org/message-id/5303F655.8000200@tpf.co.jp and http://www.postgresql.org/message-id/530551A5.7010104@tpf.co.jp > > > Regards > Andreas > > -- Adrian Klaver adrian.klaver@aklaver.com
Am 20.02.2014 17:32, schrieb Adrian Klaver: > On 02/20/2014 08:26 AM, Andreas wrote: >> Hi Hiroshi, >> >> is there an issue with new-line-conversion in the new ODBC 09.03.0100 ? >> >> I've got an PG 9.3 64bit server on Linux. >> The clients are Win XP or 7 with MS-Access 2003 or 2010. >> All ODBC are 32 bit. >> >> I've got the new-line-conversion as parameter in the connection string >> as PG uses only LF and Access needs CRLF. >> Up until V09.02.0100 the on the fly conversion works. >> >> With 09.03.0100 the line breaks in text fields get lost when displayd in >> Access. >> >> Is there a changed parameter or is there a bug in the new ODBC? > > Yes. > > See this thread: > > http://www.postgresql.org/message-id/006a01cf28e4$7c425450$74c6fcf0$@de > > In particular: > > http://www.postgresql.org/message-id/5303F655.8000200@tpf.co.jp > > and > > http://www.postgresql.org/message-id/530551A5.7010104@tpf.co.jp OK, that should be the cause of the problem. Is there a plan for a new release of ODBC as I can't use the 09.03.0100 b/c of this issue? Regards Andreas
On 02/20/2014 09:06 AM, Andreas wrote: > Am 20.02.2014 17:32, schrieb Adrian Klaver: >> On 02/20/2014 08:26 AM, Andreas wrote: >>> Hi Hiroshi, >>> > > OK, that should be the cause of the problem. > Is there a plan for a new release of ODBC as I can't use the 09.03.0100 > b/c of this issue? I'm sure there is, but when that happens is based on information above my pay grade. The developers will need to answer that. > > > Regards > Andreas
Hi. Ahh, We have recognized the fatal problem of them. It will fixed next release. probably, Ver 09.03.0200. Then, I will begin work. Regards, Hiroshi Saito (2014/02/21 2:58), Adrian Klaver wrote: > On 02/20/2014 09:06 AM, Andreas wrote: >> Am 20.02.2014 17:32, schrieb Adrian Klaver: >>> On 02/20/2014 08:26 AM, Andreas wrote: >>>> Hi Hiroshi, >>>> >> >> OK, that should be the cause of the problem. >> Is there a plan for a new release of ODBC as I can't use the 09.03.0100 >> b/c of this issue? > > I'm sure there is, but when that happens is based on information above > my pay grade. The developers will need to answer that. > >> >> >> Regards >> Andreas > > >