Haviing only one form

[azaleas]

I've a project with only one form and over 15 pages in it.

1) How would separating the pages to different forms would affect the project (performance wise)? Or is it just beneficial for readability and organization and usage? I don't feel uncomfortable with all those pages being in one form.

2) I've tried to separate the pages to relevant forms, but I got lots of errors, so I just undo the changes. What would be the best practise? How to manipulate, navigate and connect the forms together?

[Jon]

Different people have different views on this subject. You can do it either way and it should work. My personal opinion is that one form with multiple pages is the best way so long as it constitutes one single "application". Here are the main considerations:

1. Back button behaviour is much simpler and more reliable with one form/multiple pages. If you use multiple forms you have to choose between call form and goto form to navigate between the forms. If you use goto form, the back button won't work reliably. If you use call form, the back button will work, but you can have memory issues (see next point).

2. Use of call form uses more memory - this is because the system allows you to return to the calling form and therefore it keeps all the form state of all the forms - field, table values etc. If you have many page transitions, this can become quite expensive. This form state is kept in memory until the session times out - the default for this is 30 minutes but sometimes people change this to be a much higher value e.g. 8 hours or more. The combination of multiple call forms and high session timeout values can lead to excessive memory use.

[azaleas]

Thanks Jon, I'd go with your personal opinion on this one. Yes, my form with all those pages is one single application.