This post will help you to understand how to link forms and save the data to external tables which are linked by a Foreign Key Constraint.
This would not be like a wizard where users can go back and forth, it is only one way, but allows for cutting large forms into smaller units, not to mention keeping the tables from getting really wide.
So the Steps to recreate would be.
- Create the Sample Tables
- Import Each form and Map them to the Tables Created in step1
- For the first two forms set the redirect to the next form in the chain
- Submit the forms
- Run the Result Query In DNN the layout would be that the only form in the Chain which would be available for direct access by the user would be form one. As to the email at this point we could get really fancy in the last form and have a bunch of hidden fields and do a Field Query to get all the collected data up to that point and populate the hidden fields with the previous data. These extra hidden fields of course would have to be ignored by the Data Manager and not saved in the final table but only sent in the email. This and other reasons is why this is not a published feature yet as this setup is too difficult for the average user, but of course many of our users are accomplished developers themselves.