Forms with a large number of controls

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have several forms which contain either a tab control with a large number
of controls on each tab or just a single form with a large number of
controls.

Please do not comment that I should break these up into multiple forms. In
some cases it’s just not an option.

Given Access 2003 Runtime and somewhat current workstations, what is the
current thought about:

Opening these forms in the startup routine and keeping them invisible until
needed?

Opening / Closing each form as needed?

Open each form as needed and making them invisible. In case of returning to
the form it is just a matter of navigating to the correct record and make the
form visible.

Please do not comment that I should break these up into multiple forms. In
some cases it’s just not an option.
 
I have several forms which contain either a tab control with a large number
of controls on each tab or just a single form with a large number of
controls.
Click to expand...

I know whereof you speak about not being able to pare down forms...
<g>

One technique I've found useful for "overloaded" forms, especially
with multiple Subforms, is to put the subforms on separate tab pages.
Each Subform should have its Recordsource property *blank* - i.e. it
should not return any records.

In the Tab Control's Change event, use a Select Case statement to
determine which page you're opening; set that page's subform's
recordsource properties appropriately. I haven't found any better
option than to simultaneously clear all the other subforms'
recordsources (if anyone knows how to determine which page the user
was coming FROM I'd appreciate it!)

This can make a big difference, since the subforms only get populated
when needed, not on opening the form.


John W. Vinson[MVP]
 
Hi John,

Thanks, that is a good idea. Funny thing is that I do something very
similar for report subreports but it didn't event occur to the same for
subforms. All my subforms already live on individual tabs, so implementing
will be very easy.

I let you know if I find an answer to your question about which tab the user
came from.

Thanks again.

By the by
 
What page a user came from.

One method that comes to mind is to put the current page index in the tab
Control tag property. Then on the next change event, the tag (prior to you
changing it) will contain the prior page index.
 
What page a user came from.

One method that comes to mind is to put the current page index in the tab
Control tag property. Then on the next change event, the tag (prior to you
changing it) will contain the prior page index.
Click to expand...

<slapping forehead>

Yep. That would be an easy way to do it!

<off to my client's site to do just that>

John W. Vinson[MVP]
 
Why is that other people's problems are so much easier than our own?

Thanks again for the help.
 
Back
Top