Thank you.

>Like Lutz I prefer similar / mostly identical page layout - but his solution to add at bottom is not always efficient from workflow aspects. My "solution" is somewhat similar: instead of container I argue (at best for a singular) pgf to hold all the special controls needed by the user, which might add more than 1 page in the pgf. I argue for fixed placement and having "normal" data shown on page 1, but will not offer much resistance if customer offers reason for different handling. If many controls are need treatment, .setall() from .parent.parent preferred way of doing internal massages
>
>
>
>>I am wondering how others deal with the following situation. Here is how I do:
>>
>>I have a form where some customers need to see a row of controls (three labels and three textboxs). Other customer do not need to see or use them.
>>I place these controls on the form and set the Visible of all to .T.
>>At run time, when the form is initialized - based on some setting that calls for these controls not be be used - the code sets the property Visible of all controls to .F. Then, there is a LOOP through all controls and the TOP value is decreased by 26 (the space for these controls).
>>This works. But I wonder how others would do it.
>>
>>TIA