Thanks for the ideas. I will think about the alternatives.
>Hilmar,
>
>
>
>
>>>How about having each member object initialized by themselves in INIT()?
>>
>
>>Do you mean, to assign the properties? The thing is, if code somewhere changes the property at the container level, I want this change to cascade to the contained objects.
>
>I was thinking that maybe that the Assign methods for the container property should be the one to call the member/s affected to 're-load' or 're-initialize' the property values.
>
>It's like each member must have a 'reloadproperties' method which will be run in its INIT(), then the Assign of each container property will call the 'reloadproperties' method of all affected members.
>
>>
>>And for the initial value, I decided to "re-use" the assign method. I suppose I could have a separate method, which is called by the assign method, but I don't know whether this would give me any advantage.
>>
>>>
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)