Hi Dragan

This as all come about because I am trying to emulate an access system.

I think the fields really should go in a grid, but the customer much prefers to have the fields seperate on the form.

The number of "columns" can change depending on the date range for the specified period.

I've used a container class I found in the download section, which allow me to scroll the container vertically and horizontially like in access.

I though I was being clever by only creating the fields as & when they where needed, but you could be right that the best way is to create the maximum no required and making them visible as required.

Not got much time left on this project, so will be sticking with drawing as needed for now, and look at doing it the other way, if makes it faster in the end.

Thx for your input.





>>Hi Gregory
>>
>>Yeah, thought the second way was the best, but will have to subclass the control.
>
>Subclassing can be done even programmatically and on-the-fly, if you must (generate a prg with the subclass, newobject() from a class defined in it), but the additional benefit of it is that you have to think it over... since any answer here will be "depends on what you're doing".
>
>We've gone a long way from vFP5, creating new objects is fast. If you think you may be reusing some objects, then you just keep creating them as needed, hiding them when not, and when coming to create again, check if you already got one that you can use and just show it. It may also depend on what's your controlsource for them, if any - that's where it largely depends on what you're doing.