>Hi,
>
>thnx for your advice. The strange thing is that changing the "properties" memo field works 2 times... once when i'm adding the propertie second when i change the value, from there on when i'm opening the form all the standard properties for that label are gone ...(but they r still in the scx file)
>
>Opening the scx file and making a change in it makes tht when opening the form the properties r back.
>
>The problem is that the added propertie contains the translation of the caption off the conserning label. So that we can translate all our labels in just a sec expl from English to french.
>
>As we r still working in vfp5 i can't follow yr advice concerning vfp6.
>
>Do you know a good alternative for a translation off all the label on a form ?
>It's important tht we also keep the original translation some where.
>
>(don't tell me to start using vfp6 :o))
>
>thnx
Oh Kurt,
Your main concern was to change caption. Then I think creating a label class of your own would be an easier solution. Label class could be something like :
Language = 1
select * from myTranslator ;
where English == this.Caption ;
into array arrTemp
if _Tally > 0
this.Caption = arrTemp[1,this.Language]
endif
At design time click on any control on form, go to command window :
aselobj(arrForm,1)
arrForm.SetAll('Language',2) && Set to French
When you run the form you'd see missing captions left at their default English. I would use this for just design time and keep language version in an app wide property. Otherwise each language version would need a separate compile (init would then use oApp.Language rather then this.Language).
Cetin