Since this was the only reply, does that mean javascript is the only way
to do this?
It's the only way to do it interactively. You could also post the form when the user selects from a menu and rebuild the menus when the page reloads.
How do you keep track of the changed fields when moving from page to page
within the "input" form?
Do you store each page's values in Collections (using A4D)?
Yes, that is what sessions are for.
When the time comes to save the record, do you then reload the actual record and copy the values back into the fields?
Yes.
Even that is going to be *very* tricky as there are 10 input form pages,
many of which contain included forms which take you into their Input
forms, and some can go beyond that.
Unless you have an inordinately large amount of data in a record (like 1MB) and you anticipate having dozens of users editing records at the same time, you have nothing to worry about. Just store it all in the session.
I am starting to get scared I am trying to do something unrealistic.
There is nothing unrealistic about it. The technique is the same whether you have one page or ten. It's just a matter of scaling the technique.
Regards,
Aparajita Victory-Heart Productions [EMAIL PROTECTED] www.aparajitaworld.com
"If you dare to fail, you are bound to succeed." - Sri Chinmoy | www.srichinmoylibrary.com
