Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

problem reading a field string with accent

3 posts in ODBC Last posting was on 2009-04-06 16:23:51.0Z
Simone Degl'Innocenti Posted on 2009-04-06 11:08:19.0Z
From: "Simone Degl'Innocenti" <hot@albalog.it>
Newsgroups: Advantage.ODBC
Subject: problem reading a field string with accent
Date: Mon, 6 Apr 2009 13:08:19 +0200
Lines: 29
Organization: Albalog s.r.l.
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 213.255.125.48
Message-ID: <49d9e280@solutions.advantagedatabase.com>
X-Trace: 6 Apr 2009 05:07:44 -0700, 213.255.125.48
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!213.255.125.48
Xref: solutions.advantagedatabase.com Advantage.ODBC:1812
Article PK: 1133189

Hello

I'm using ADS server 8 via ODBC connected to an advantage dictionary to read
DBF/NTX tables.
The DBF/NTX tables are mainly written by an Xbase++ application (via ADSDBE)
without accessing the advantage dictionary.

I have problems reading tables that contains character > 127 (for example
accent) via ODBC; with Xbase++ it is ok.

With ODBC the statement
SELECT NOTART FROM ARTICOL WHERE CODART='xxx'
returns the string "umidit." but if I check with Xbase++, in the memo field
there is the string "umidit?"

I have the same problem for character and memo fields.

The ADS server is configured as ANSI=ITA OEM=ITALIAN.

I tried changing the "character set" from ansi to oem in the ODBC connection
and I tried also changing the OEM configuration of the ADS server (before it
was OEM=USA now it is OEM=ITALIAN), but I still have the same problem.

How to solve this problem?

Thanks
Simone


Mark Wilkins Posted on 2009-04-06 14:41:30.0Z
From: "Mark Wilkins" <mark@no.email>
Newsgroups: Advantage.ODBC
References: <49d9e280@solutions.advantagedatabase.com>
Subject: Re: problem reading a field string with accent
Date: Mon, 6 Apr 2009 08:41:30 -0600
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Response
NNTP-Posting-Host: 10.24.38.228
Message-ID: <49da1474@solutions.advantagedatabase.com>
X-Trace: 6 Apr 2009 08:40:52 -0700, 10.24.38.228
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!10.24.38.228
Xref: solutions.advantagedatabase.com Advantage.ODBC:1813
Article PK: 1133190

Hi Simone,

When a table is in a data dictionary, the character type (ANSI or OEM) is
stored with the table. It overrides the ODBC connection setting. It sounds
like the table was added to the dictionary with character type ANSI. You
probably need to add the table to the dictionary with character type OEM. I
don't think it is possible to change the character type after it has been
added. So it would be necessary to remove it from the dictionary and then
add it again with the correct type.

Mark Wilkins
Advantage R&D

"Simone Degl'Innocenti" <hot@albalog.it> wrote in message
news:49d9e280@solutions.advantagedatabase.com...
> Hello
>
> I'm using ADS server 8 via ODBC connected to an advantage dictionary to
> read DBF/NTX tables.
> The DBF/NTX tables are mainly written by an Xbase++ application (via
> ADSDBE) without accessing the advantage dictionary.
>
> I have problems reading tables that contains character > 127 (for example
> accent) via ODBC; with Xbase++ it is ok.
>
> With ODBC the statement
> SELECT NOTART FROM ARTICOL WHERE CODART='xxx'
> returns the string "umidit." but if I check with Xbase++, in the memo
> field there is the string "umidit?"
>
> I have the same problem for character and memo fields.
>
> The ADS server is configured as ANSI=ITA OEM=ITALIAN.
>
> I tried changing the "character set" from ansi to oem in the ODBC
> connection and I tried also changing the OEM configuration of the ADS
> server (before it was OEM=USA now it is OEM=ITALIAN), but I still have the
> same problem.
>
> How to solve this problem?
>
> Thanks
> Simone
>


Simone Degl'Innocenti Posted on 2009-04-06 16:23:51.0Z
From: "Simone Degl'Innocenti" <hot@albalog.it>
Newsgroups: Advantage.ODBC
References: <49d9e280@solutions.advantagedatabase.com> <49da1474@solutions.advantagedatabase.com>
Subject: Re: problem reading a field string with accent
Date: Mon, 6 Apr 2009 18:23:51 +0200
Lines: 55
Organization: Albalog s.r.l.
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: 213.255.125.48
Message-ID: <49da2c66@solutions.advantagedatabase.com>
X-Trace: 6 Apr 2009 10:23:02 -0700, 213.255.125.48
Path: solutions.advantagedatabase.com!solutions.advantagedatabase.com!213.255.125.48
Xref: solutions.advantagedatabase.com Advantage.ODBC:1814
Article PK: 1133191

Hello Mark

You are right, I fixed the data dictionary and it is ok now, thanks!
Simone

"Mark Wilkins" <mark@no.email> ha scritto nel messaggio
news:49da1474@solutions.advantagedatabase.com...

> Hi Simone,
>
> When a table is in a data dictionary, the character type (ANSI or OEM) is
> stored with the table. It overrides the ODBC connection setting. It
> sounds like the table was added to the dictionary with character type
> ANSI. You probably need to add the table to the dictionary with character
> type OEM. I don't think it is possible to change the character type after
> it has been added. So it would be necessary to remove it from the
> dictionary and then add it again with the correct type.
>
> Mark Wilkins
> Advantage R&D
>
> "Simone Degl'Innocenti" <hot@albalog.it> wrote in message
> news:49d9e280@solutions.advantagedatabase.com...
>> Hello
>>
>> I'm using ADS server 8 via ODBC connected to an advantage dictionary to
>> read DBF/NTX tables.
>> The DBF/NTX tables are mainly written by an Xbase++ application (via
>> ADSDBE) without accessing the advantage dictionary.
>>
>> I have problems reading tables that contains character > 127 (for example
>> accent) via ODBC; with Xbase++ it is ok.
>>
>> With ODBC the statement
>> SELECT NOTART FROM ARTICOL WHERE CODART='xxx'
>> returns the string "umidit." but if I check with Xbase++, in the memo
>> field there is the string "umidit?"
>>
>> I have the same problem for character and memo fields.
>>
>> The ADS server is configured as ANSI=ITA OEM=ITALIAN.
>>
>> I tried changing the "character set" from ansi to oem in the ODBC
>> connection and I tried also changing the OEM configuration of the ADS
>> server (before it was OEM=USA now it is OEM=ITALIAN), but I still have
>> the same problem.
>>
>> How to solve this problem?
>>
>> Thanks
>> Simone
>>
>
>