>>It's probably just me not understanding, but:
>>
>>Does that mean that different objects might be translated into different languages? You might have labels that are French, German, English and Swahili all in the same application instance?
>>
>>If so, maybe a property defining the particular object's language in the base class would be the way to go, and then a caption property (or in the init) =Translate(This.Caption, This.cLanguage).
>>
>>If not, then I'm having trouble understanding the problem. It seems like a caption of =Translate(This.Caption) or even Translate(This.Caption, gcLang) should be enough. Or as Mike pointed out, in the init.
>
>
>
>Every object is translated to the same language.
>But the same caption doesn't translate the same in all places.
>For example, when translating to Portuguese:
>
>The Caption «Quote», can have different Portuguese Translations depending on the Context.
>
>So, in order to correctly translate this caption, instead of having:
>=Translate(This.Caption)
>I would have to have:
>=Translate(This.Caption,cObjectKey)
>
>Where cObjectKey is something that identifies the context, the place where that caption is used.
>
>So when the Caption «Quote» is used in some class, it should be translated as one thing, and when that same caption is used in other Class, or in some other Form, it should be translated as another diferent thing.
>
>So you see, I MUST have information about tha place (in code) where the Value of Caption was defined

Not true at all. All you need to do is have a different key phrase for each context. QuoteContext1 gets translated one way and QuoteContext2 gets translated another way. No need for all the fancy object genetic mapping.