>Hi Dragan,
>
>I see. Loading a class dynamically at a later time is your problem. The way I implemented this in one of the frameworks is to instantiate these objects through a factory. The factory would receive an ID, look up the definition and find that it needs to instantiate two classes. One is the data environment, one is the actual class. The DE was made available through a property and (for the duration of the Init) through a private variable.

Which works fine with one per form. However, I have multiple, and so I don't have the luxury of using .load() to do such work, and the loader object placed on the grandest parent container class doesn't guarantee to be instantiated first, not anymore.

Anyway, calling the factory via an expression in the property does work, so we have another trick up our sleeve :).