[AccessD] Wish List.

I never do multipage without tab controls, there are just too many drawbacks
and problems otherwise.  Each tab page contains either controls or subforms,
which contain controls.  It depends on whether the entire form is bound to
one data set or each page draws from different sources.  That eliminates the
need for a complicated query behind the main form because each subform on
whichever tab page has its own data source and is bound to the parent
dataset using the master/child links or bound JIT.  Alternatively (JIT),
unbound subforms are populated from code based on whatever criteria are set
at the parent level, but not until the tab page has been selected.

On Thu, Sep 8, 2011 at 10:47 AM, Mark Simms <marksimms at verizon.net> 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.
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
>
>
> Website: http://www.databaseadvisors.com
>
>
>