Page 1 of 1

AutoTranslate problems with blob field and accent characters

Posted: Wed 18 Jun 2008 15:16
by rodbervilato
I´ve been trying to use a MsQuery to return a Blob field. In order to get the result of this field properly, I have to change the AutoTranslate property to False, since with this property set to true, the component returns the results in a wrong way (everything is twisted). If this result is a text file, the result comes as a incomplete file and with its line in changed positions).

I cannot set the Autotranslate property to false, as it is for default, since all fields which contain accent characters, are returned with odds symbols! Adjusting this property to true, these accent characters will be right, but I cannot return field blobs correctly.

Can you tell me if is there any other property to allow to work properly with both situations?

Database properties:
MSSQL Sever : SQL Server 2000
Collation : SQL_Latin1_General_CP850_CI_AI
Field type : varchar
Blob type : Text

Posted: Fri 20 Jun 2008 11:17
by Antaeus
Please send us a small database containing one table with some data to reproduce this problem. Also specify:
- the language of your client operating system;
- the language for non-Unicode programs;
- the exact version of SDAC. You can see it in the About sheet of TMSConnection Editor;
- the exact version of SQL server and client. You can see it in the Info sheet of TMSConnection Editor.

As a possible solution I can suggest switching field types from VARCHAR to NVARCHAR, etc.

Posted: Mon 23 Jun 2008 18:38
by rodbervilato
After I have sent to you a report describing my problem, I decided to make some more tests in order to get a logical explanation. I´ve decided to use your demo application, where I could notice that the problem is still happening. After I checked that the demo version was still presenting the same bug, I decided to test in other machines, that´s when I´ve found a machine on which that error does not occur. This behavior has led me to check the OLEDB driver version, and I could notice that the error occur only when we are using the "prNativeClient" provider with MS Sql Server 2000. For data bases located in SQL 2000 Servers it´s necessary a "prSQL" provider. When using a SQL2005 it´s necessary do use a "prNativeClient" provider.

thanks for help.