[V4RB2] Convert_v1_v2 problem

[Stan Busk]

Hi,

Do you think that should be object for a feature request? I mean the  
possibility to use a flag when changing the type of a field in order  
to keep the data it already contains? It would be really handy in  
cases like mine where the new type is same size or when new type is  
bigger. Doest it make sense? That would allow to correct design  
problems or to update a type to a bigger one. Do you think it is  
possible to implement? I guess you can do that in 4D or am I  
dreaming? I am worried about the fact a design problem has no  
solution and you have almost 10k people using your software :(

~/Stan

> On 2/23/06 11:05 PM, "Stan Busk" <maxprog at mac.com> wrote:
>
>> I mean I could save the value, change type and then apply the value
>> again. I guess this is possible and it will allow me to recover from
>> the bad design I use for that old project. Something like:
>>
>> temp = vdb.Table( "myTable" ).ULongField( "myRecIDField" ).Value
>> vdb.Table( "myTable" ).Field( "myRecIDField" ).Type =
>> EVFieldType.kTypeObjectPtr
>> vdb.Table( "myTable" ).ObjectPtrField( "myRecIDField" ).Value = temp
>>
>> I guess that with that code I will end with a replacement ObjectPtr,
>> or no? :P
>
> I understand what you want. I believe answer is no.
>
> New ObjectPtr field will get ZERO value.
>
>
>> ~/Stan
>>
>>>
>>> You mean if you can CHANGE TYPE for them ?
>>>
>>> I afraid Valentina set ZERO that column,
>>> Because we assume that old values cannot be correct RecID values.
>
> -- 
> 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]
>
>
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina