[V4RB] Hight ASCII value in virtual field method (was Re: [V4RB] -39 Error)

[Ruslan Zasukhin]

on 5/20/03 9:26 PM, Francois Van Lerberghe at fvanlerberghe at freegates.be
wrote:

>>> I have normal (not virtual) fields name with chars > 127. I have done this
>>> because, unfortunately, I ignored the problem at the design time and I
>>> haven't time now to change this.
>> 
>> Aha, I see now. Name of field.
>> 
>>> These fields name are portable ("correctly translated"). But If I use one in
>>> method, the chars are incorrect when I go to the other OS
>> 
>> I think I can fix this.
> 
> Oh, very, very nice :=)))
> This will help me a lot and made possible the use of db across multiOS
> network.
> 
> As you will be with this kind of problem, note that there aren't any
> conversion with text field (no trouble with string or varchar). So if I
> store text value with high ASCII value on MacOS, I'll have incorrect text on
> Windows. But perhaps you will say that it's my job...

Hmm, it seems you again describe 2 problems.

You mean that EACH Text field, do not convert its value ???
I am sure it do convert it, as well as String and VarChar.
A lots of Valentina for Director developers use this feature.
They make db on one platform and read it on any platform.
You need double check, why you think so.

For BaseObject method, yes, I could miss this point.

-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://lists.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------