>>>>
>>>>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.
>>>
>>>That way, the developer would have to Generate the Context Key himself, each time he modified the Caption (the same goes for StatusBarText and ToolTipText). I would have to have a property in all my objects for the developer to tap in a ContextKey each time he droped a control on a form or change it each time e copied and pasted an object from somewhere else.
>>>
>>>What i'm doing here is avoiding the developer that need.
>>>So thedeveloper doesn't have to generate any contextkey. He just writes the Caption of the object on the property sheet.
>>>
>>>I simply use the ObjectPath/ClassPath as the ContextKey.
>>
>>and taking a potentially big performance hit checking the genetic mapping of every object as well as translating the caption.
>
>You are completely right. That's my big fear.
>I already have a performance hit for the translation of the caption.
>Fabio's solution enables me to find that well named genetic mapping of the object. It uses ACLASS and GETPEMS. I'll see if the outcoming performance hit will be acceptable or not.

Glad to hear it. Consider also that if there are only 2 contexts for quote, there should only be 2 entries in your translation table. If I understand, you will be expanding the table too much because each object in each form will require its own translation.

I hope it works out well.