Hi!

Look o following and think what is better for you.
Say, you want to do everything just by call of the container.Refresh and enable/disable controls by refresh methods of controls. Than, in refresh method for EACH control that change its state depended on certain criteria, you will require to write code AND define that criteria exactly. Here the complexity is in the defining criteria for eachsuch control, define the refresh methods. In addition, maintenance is complex because you have everything in different spots hard for search and changes. This have an advantage, however - encapsulation. This way is more code-reusable.

If you write everything in a single procedure, you will require to list al items depended first, than switch their state depended on data in that routine. The complexity here is only in listing of all controls that have ttheir state depended on data. Determining of criteria is less complex because here you can work with groups of controls. And no maintenance troubles - any change you will do in the same routine that is much more easy. However, code-reusability is near impossible to reach in such case. If you plan to use bits of these controls in other different places, you will probably require doing a copy.

HTH.

>Hi
>
>I have a form that is rather complex in the way it displays itself.
>
>I have a couple of comboboxes, and then below them I have 2 containers (invisible) that contain other objects. The containers will only be visible when they are required, so they will be made visible dynamically.
>
>The objects inside the containers will also be enabled/disabled depending on meeting certain criteria....
>
>Right.....!!
>
>Providing you understand what I mean (various rules/different scenarios), can anyone advise me on the best way to strucuture this sort of programming.
>
>Should each object have it's own code in the refresh?
>Should the controls be manipulated from just 1 program?
>
>Any ideas, the rules behind them are pretty complex.
>
>Let me know if you need more info.
>Thanks
>Kev