If you had a subform for each button, that many subforms would be
unmanageable in design view. You wouldn't be able to distinguish one from
another to work on any of them. Add a tabcontrol to your form, create as
many pages as you need and put a subform on each page. In design view, you
can click the tabs and easily go from one subform to another. When you have
the system built, turn the tabs off and then you just need to add a system
of buttons in an option group to go from one page (subform) to another. It's
a very neat system done this way.
--
PC Datasheet
Your Resource For Help With Access, Excel And Word Applications
resource@pcdatasheet.com www.pcdatasheet.com
<dmkeith2@hotmail.com> wrote in message
news:1111890828.309448.313540@z14g2000cwz.googlegr oups.com...[color=blue]
> Thanks,
>
> It's a demo, but it's an MDE so I can't look in design view. I believe
> it is various subforms that are hidden and unhidden based on the
> buttons being pressed.
>
> Do you know how to unhide subforms and once a different button is
> pressed it hides all other subforms and unhides the one it calls.
>
> I'm sure the guy that did this database used some sort of source object
> call but I'm not that good. Thanks
>[/color]