Oracle 9.2 with OLE DB
Oracle 9.2 with OLE DB
OLE DB works fine, even the input message buffer problem does not exist. However, attempting to read LONG VARCHAR from Oracle 9.2 (non-UNICODE) into a table window column results in non readable chars. (All chars are block symbols, all the same)
You do not have the required permissions to view the files attached to this post.
Re: Oracle 9.2 with OLE DB
Hi Martin,
As far as I know LONG VARCHAR does not exist on ORACLE. So you meant LONG or CLOB. Can you clarify please. Knowing about the CHARSET of the database and the NLS_LANG would help to.
One though about this, when you see those blocksit might be related to font, I had a greek application were on my machine Table Window showed those blocks but not on customer greek machine. Can you try to change the font in windows default/child TBLW to be Arial Unicode MS
it is just a sugestion...in waiting to know more from you.
Jean-Marc
As far as I know LONG VARCHAR does not exist on ORACLE. So you meant LONG or CLOB. Can you clarify please. Knowing about the CHARSET of the database and the NLS_LANG would help to.
One though about this, when you see those blocksit might be related to font, I had a greek application were on my machine Table Window showed those blocks but not on customer greek machine. Can you try to change the font in windows default/child TBLW to be Arial Unicode MS
it is just a sugestion...in waiting to know more from you.
Jean-Marc
Re: Oracle 9.2 with OLE DB
Hello Jean-Marc
Martin Diestelmann logged this bug in my behalf during our test-migration at his location. So I guess its ok if answer your question directly.
It ist a LONG Datatype. NLS on DB ist NLS_CHARSET=WE8MSWIN1252, NLS_LANGUAGE=AMERICAN and on the Client is NLS_LANG=GERMAN_SWITZERLAND.WE8MSWIN1252
Font should not be a problem here, cause its all Standard and if I fetch the Data to a LongString in TD ist also not readable.
Thomas
Martin Diestelmann logged this bug in my behalf during our test-migration at his location. So I guess its ok if answer your question directly.
It ist a LONG Datatype. NLS on DB ist NLS_CHARSET=WE8MSWIN1252, NLS_LANGUAGE=AMERICAN and on the Client is NLS_LANG=GERMAN_SWITZERLAND.WE8MSWIN1252
Font should not be a problem here, cause its all Standard and if I fetch the Data to a LongString in TD ist also not readable.
Thomas
Who is online
Users browsing this forum: [Ccbot] and 1 guest