[V4RB] -39 Error

[Ruslan Zasukhin]

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

>>> This error is related to the corruption of some String fields (containing
>>> bugged values : strange characters displayed in VAPP). Fortunately, This
>>> happen in only one table that have only one record.
>> 
>> I think for VarChar fields. String field practically cannot be corrupted.
> 
> These was String fields. No VarChar in this table.
> Is it possible that the structure update has made some offset that perhaps
> is not the same in Win32 and in MacOS ?
> The structure update was this one :
> I have decreased the length of 2 String fields (3 -> 2) in 2 tables (one
> field in each table). These table was not the same as the "corrupted" table.

You mean you have made changes in this 2 tables,
But corrupted become third table ???

 
>> I think you have made some mistake.
> 
> my code is :
> 
> newLength = 2
> myStringFld.maxLength = newLength
> 
> This seems to work well. No error raised

You have made this ONCE, when you have upgrade version of db ?
Yes?


>> IT looks you describe 2 problems.
>> 
>> 1) BaseObject method with chars > 127 is not portable?
> 
> No
> 
>> why this characters here?
> 
> 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.
I need check it.

-- 
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
-------------------------------------------------------------