[AccessD] How do I create list of all forms/subforms

Darryl Collins Darryl.Collins at iag.com.au
Tue May 24 21:28:29 CDT 2011


_______________________________________________________________________________________

Note: This e-mail is subject to the disclaimer contained at the bottom of this message.
_______________________________________________________________________________________


That is a great approach. Using regular modules also makes the code much easier to transfer to another app with little or minor changes.  If you are using form code that is not always as easy to do.


________________________________________
From: accessd-bounces at databaseadvisors.com [accessd-bounces at databaseadvisors.com] On Behalf Of Stuart McLachlan [stuart at lexacorp.com.pg]
Sent: Wednesday, 25 May 2011 11:47 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] How do I create list of all forms/subforms

I gave up on shared subforms a long time ago - had too many situations where new
requirements meant that the same sub-form no longer worked on both master forms.

Like you , I try to keep event procedures down to simple function calls with all the grunt work
done in standard modules.

--
Stuart


On 24 May 2011 at 21:23, William Benson (VBACreations. wrote:

> Works fine if ... you don't share subforms between multiple forms. I
> suppose you could always just duplicate the subforms, but I find
> keeping the code synchronized between multiple copies a mild hazard.
>
> Of course lately I have been calling procedures and functions stored
> in standard modules, when events on my forms and subforms run ... so
> it hasn't been as big a deal.
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Stuart
> McLachlan Sent: Tuesday, May 24, 2011 6:09 PM To: Access Developers
> discussion and problem solving Subject: Re: [AccessD] How do I create
> list of all forms/subforms
>
>  That's why I use a naming convention in complex applications that
> specifically identifies subforms and keeps them together in the forms
> list :-)
>
> frmMain
> frmMain_subCustomersList
> frmMain_subCustomerDetails
>
>
>
> > I want to generate a list of all the forms and their subforms in my
> > application (whether loaded or not). Right now I'm looping over
> > Application.CurrentProject.Allforms and getting the name of every
> > form, but the object doesn't distinguish a subform from a form. I
> > tried the Type property but they're all Type 2. Is there a routine
> > out there I can scarf? Thanx, Darrell
> >
> > --
> > 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
>



--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
_______________________________________________________________________________________

The information transmitted in this message and its attachments (if any) is intended 
only for the person or entity to which it is addressed.
The message may contain confidential and/or privileged material. Any review, 
retransmission, dissemination or other use of, or taking of any action in reliance 
upon this information, by persons or entities other than the intended recipient is 
prohibited.

If you have received this in error, please contact the sender and delete this e-mail 
and associated material from any computer.

The intended recipient of this e-mail may only use, reproduce, disclose or distribute 
the information contained in this e-mail and any attached files, with the permission 
of the sender.

This message has been scanned for viruses.
_______________________________________________________________________________________




More information about the AccessD mailing list