Access should treat tab control pages as seperate forms

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

Guest

This would make it easier to design tab controlled forms becasue having to
deal with subforms is negated by the fact that each tab page on the tab
control is treated as a seperate form. This would allow for a much better
front end design for the end user and make the coding for form selection much
easier concerning the tab control.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...bedf61fb2c56&dg=microsoft.public.access.forms
 
Hi,



You have, actually, a design where the controls belong to the "main" form
and are just displayed, or not, depending of the active tab. To access the
various control, you just access them as if the control was a standard one
in the form.

You can use a subform per tab. That may be a little bit slow (for navigation
between records), but you then have "separate forms" for each tab. To access
the controls in these subforms you have to use the form-subform syntax.


So, with the actual design, you have both worlds possible.


I fail to see the point you elaborate: having different "form", one per tab,
that means that two tabs can have a form with a control name, for
illustration, Text1. So, how would you differentiate them, in the main form,
if not by using a form-subform syntax ?



Hoping it may help,
Vanderghast, Access MVP
 
Back
Top