[AccessD] Wish List.

I also think there is some confusion about what page means.

There is actually a page control which if inserted on a form causes the form to "page down" when the 
page down control is hit.  It is nothing more than a tiny little control that is inserted at some 
point vertically in the form.  I never use it because it feels clunky.

What another lister was discussing is dynamically loading forms as the user moves through "pages" of 
a wizard.  that is completely different.  In that case all of the controls are literally in a 
subform which is of course just another form.

John W. Colby
www.ColbyConsulting.com

On 9/8/2011 1:47 PM, Mark Simms wrote:
> I think there is some confusion here over multipage vs. tab controls.
> I never really determined how/when to use the latter.
>
>> -----Original Message-----
>> From: accessd-bounces at databaseadvisors.com [mailto:accessd-
>> bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
>> Sent: Thursday, September 08, 2011 11:56 AM
>> To: Access Developers discussion and problem solving
>> Subject: Re: [AccessD] Wish List.
>>
>> I do know how they work, but I was confused by what I understood of
>> your
>> description.  What you're describing is exactly what tab controls are
>> for,
>> and I've used them that way in both Access and VB.Net.  All you need to
>> do
>> with a tab control is select the tab page and that brings the controls
>> on
>> that page up for you to edit.  In effect, you see them the way the user
>> does, except for any controls that you make conditionally visible to
>> the
>> user when that page is up.  Those, of course, you see in design view
>> all the
>> time.
>
>