help thinking through this complicated form design
I hope this is the appropriate place to post this.
I have an existing form using PEAR HTML_QuickForm that works fine. But...the database and logical design has changed a little. Formerly, the database record was related to a company. now the record has "child" records - records related to this record.
I want a form that represents this easily to the user. So I thought of a form with some basic record information with the option of adding child records on that same form.
The problem with that is:
1- you never know how many child records there might be
2- if you do a page refresh, with saving first, current field data will be lost for new records - no easy way to work-around in HTML_QuickForm.
Ideally, I could refresh the page as they add a new child record and it would display a link to that new child record. This would work except if they edit the field on the main record page since it would not be saved when page is refreshed without saving first - see above. Clear as mud?
Should I have one form for editing basic main record data then another for viewing that data and editing/adding new child records? Or is there another way around it?