Multi-page form?

[Yeahyeahyeah]

Hi,

I have rather large form with lot of fields to be filled in. Rather than
having one large page that users will have to scroll down and down and down
to fill in, is there a way to break the same thing up into a series of
separate, smaller pages/screens so that users can fill in a few fields, click
on a command button that says "Next Page" and continue from there. I know I
can set up several separate forms, but how do I link them so they feed to the
same record in the underlying table?

Thanks for the help!
YYY

 

[vbnetman via AccessMonster.com]

Perhaps tabbed pages could solve some real estate issues.

hth

 

[Yeahyeahyeah]

Ok, great. That's working. So here's the next challenge. Because I need to
closely control the sequence that the tabs are used I want to set the tab
style to "none" and use a command button within the Details section of the
tab to go to the next tab. I've read about 20 posts on "tab control" and
"comand buttons" but still can't figure out how to program the Command Button
to go to the next tab.

Any suggestions?

Thanks, YYY

 

[Cheese_whiz]

Hiya yeahyeahyeah,

One thing you can consider as an option is hiding the second and third
tabs/pages until some condition is true on your main page. For example, in
one of my apps I have a three tabbed form. When a new record is showing, the
form shows only one tab (the "main" tab). After someone types in some info
and saves the new record, the other two tabs become visible. I've done it
that way because the other two tabs MUST be associated with a record and so I
make them visible on the "after update" event of the form.

For me, all I had to do was set the tabs to not be visible in a new record.
Then, in the sub form_afterupdate event of the form, I make them visible.

Anyway, you could make them visibile on any number of events or field
changes or whatever.

Hope that helps,
CW

 

[vbnetman via AccessMonster.com]

yyy,
Can separate forms be an option? This may work as you like. If not, and you
want to use a command button, create it on, say, page 1 (first tab). In the
onclick event of the button add the code
page2.setfocus.(this assumes that page2 is the name of the second page).
Repeat for any additonal pages. If I'm understanding what you want, this
should work. Let me know if this is a fix for you.

hth
vbnetman

Ok, great. That's working. So here's the next challenge. Because I need to
closely control the sequence that the tabs are used I want to set the tab
style to "none" and use a command button within the Details section of the
tab to go to the next tab. I've read about 20 posts on "tab control" and
"comand buttons" but still can't figure out how to program the Command Button
to go to the next tab.

Any suggestions?

Thanks, YYY

Perhaps tabbed pages could solve some real estate issues.

[quoted text clipped - 12 lines]