- To simulate a wizard made of a small number of steps (ie, Step1, Step2,
Step3), with different userControl for each step, always at the same
position, while the end user allowed to navigate forward, or backward, or
"finish" the process, from other controls on the form.
- To present different type of data from a super group of data. Example, a
list of bills (database navigation through the bills): while different bills
have data in common for all kind of bill, some details may differ for a bill
about electricity, or for a bill of gas; and having many controls
'unselectable' or 'invisible' accordingly to the exact type is not "as
nice as" a specific ad hoc userControl (always at the same place, on the
form, and 'filling' the space 'nicely', without 'holes' here and there).
In fact, both of these scenarios are directly 'taken' form the 'sub-form'
concept in Access (where you don't really superpose multiple controls, but
have just one where you specify its property "source object" accordingly to
the 'form' to be displayed, at run-time, as the situation requires it).
Vanderghast, Access MVP