If you have several forms that are interactive, using the include method allows you to work on each individually with a different file name in the editor.

This saves you scrolling up and down or using single file bookmarks which can be a pain. Name each file so that it has a reference to the switch condition in it and it makes it even more intuitive.

The top level switch file is very usefull for testing for form to form jumps. As the sub forms all point to the main switch file with a pointer to where they would like to jump to, you can do checks to see if all fields are filled before allowing the form jump.

If there is a field unfilled you can trap this and change the switch pointer to load the original form up highlighting the fields that have been missed.

Also, to make things easier to handle, all of the state control code can be grouped at the bottom and the top of the top level switch form. The sub forms can then concentrate of display issues.

You may also find - as I did - that the top level form then becomes more of a descriptive document that explains the interform logic.

This is home grown but I have used it well with up to five interractive forms. I would be interested to hear if anyone has taken this sort of approach any further.