[AccessD] Wish List.

Dan Waters df.waters at comcast.net
Fri Sep 9 07:59:51 CDT 2011


Not true!  Since you're already setting the Sourceobject of the subform by
code, you can do the same with the master/child link properties.  When I did
this, the master/child were the same anyway, which I'd guess in Darryl's
case would also be true.

Dan

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, September 08, 2011 10:14 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Wish List.

Yeah, there is, but only if you're using bound subforms.  If they're
unbound, it isn't a problem! ;->

When using bound subforms, the master/child links have to be cleared and
reset, which is a great argument for using unbound subforms.  This is
essentially what I've done with tab controls, except that with the tab
control option, you don't have to clear and reload the subform control each
time, which will create a delay, although perhaps not a noticeable one if
the subform and its source are straightforward.  The tab control only has to
load the subform once when you go to a particular tab page.  After that, the
tab control takes care of hiding and displaying it.  And binding isn't a
problem.

Charlotte Foust

On Thu, Sep 8, 2011 at 6:16 PM, William Benson
<vbacreations at gmail.com>wrote:

> I like that concept. Any downside you're hiding from us?
>
> ;)
> On Sep 8, 2011 9:06 PM, "Dan Waters" <df.waters at comcast.net> wrote:
> > I haven't completely read each post so maybe this has already been
> brought
> > up.
> >
> > On your form, create a subform. Now create a form to use in that 
> > subform, with all the controls from one of your 'layers'. Then 
> > create (start by
> > copying?) all the forms (as layers) that you'll want to use in the
> subform.
> > In your main form, write code to change the SourceObject property to 
> > the name of whichever form you want to display depending on what 
> > your user
> needs
> > to do. You might want to use Application.Echo False/True in code to 
> > surround the switch from one form to the other to minimize screen
> flashing.
> >
> > This separates out each group of controls onto its own easily 
> > editable separate form, and gives your user a clean GUI which 
> > doesn't have the
> tabs
> > of a tab control. I have used this and it works fine.
> >
> > You can so the same thing with a subreport control on a report.
> >
> > HTH,
> > Dan
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
>
>
> > Website: http://www.databaseadvisors.com
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
>
>
> Website: http://www.databaseadvisors.com
>
>
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com





More information about the AccessD mailing list