> True, but the forms (there are several, depending on the category of
information being entered) is quite lengthy and--for ease of development &
maintenance--was hoping to use one form for each.
That said, I will probably go ahead and use separate forms for each
(add/edit) and hope the client isn't change order happy.
Always include the unchanging parts in order to ease development & big
fixes. Another thing is, that client should see what makes him happy. But he
is not propably interested in how you do it?
Make copy-paste scripts in internet are all-in-one-form type, but I ahve
also discovered that it makes things messy, when you have to speculate "if
elseif...." all the time.
Usually I have do my forms like this:
<form action="adfsdfas">
<input type=hidden name=sender value=add_record>
......
<input type=submit name=sub value="ADD">
<input type=submit name=sub value="DO SOMETHING ELSE">
</form>
This way I have more freedom to name submit buttons the way I want, even I
can have same names in different forms, because sender (or it could be also
just the name of the form!) separates them. Of course I could speculate the
name of the submitbutton instead of its value, but it results more
dirtylooking code.