Encoding of 1-2 converted db

[Ruslan Zasukhin]

On 10/14/05 4:08 PM, "Leo Van den Brande" <leo_van_den_brande at wxs.nl> wrote:

Hi Leo,

> After conversion of a database from Val 1 to 2 I experience an encoding
> problem.
> 
> I develop on Mac OS 10.2.6 with Realbasic 5.5.2.
> 
> With Val 1, I applied conversion to MacRoman for Mac and WindowsLatin1 for
> Windows, both on storage and retrieval. This worked well.

Just REMOVE all this code with v2 !!!
 
V4RB expect to see RB String in UTF8 format

> According to the documentation and discussions, Val2 delivers UTF8 format
> which is Realbasic format.

right
 
> So, I queried with:
> c  = App.mValdb1.SQLSelect(s,EVCursorLocation.kServerSide,
> EVLockType.kReadOnly, EVCursorDirection.kRandom)
> 
> and retrieved a string with:
> aResult = c.Field(<some field name>).GetString
 
> Accented characters do not show correctly in RB on Mac.

> I tested many alternatives on Mac: convert encoding to MacRoman on retrieval,
> convert to MacRoman after retrieval, but none was successful.

NO NEED to convert anything !!!
 
> On Windows, the converted DB caused errors on opening. I have not yet examined
> that problem and first want to focus on the behaviour on Mac.
> 
> Note that this code works perfectly well with a new db created on Mac, also
> when ported to Windows.

"This code"?  Above code?

So have I correctly understand, fresh db created by V2 works fine,
But converted_1_2() do not work accents.
Right ?

What language was in v1 database?


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]