Why use multiple submission tasks?
Before I answer this question, let me answer an obvious question: Since many forms are better suited to a single submit button, why do people sometimes need two (or more) submit buttons?
The best way to explain this problem is to use an example from my recent development project. In this project, my task is to build a detailed catalog query system for a library. Book titles are stored in a database, and administrators will be able to use a browser-based interface to view records for any book and then choose to perform one of four operations on that record: member return registration, Member borrowing registration, book loss records and book sales records.
All the above tasks must be handled through a separate form, so corresponding buttons are needed to respond to these tasks. Data passed into the form will be processed in different ways, depending on which button is clicked (borrow/return and member records are related to each other; loss/sale records change the inventory table). Since a form can only handle one unique task, the same PHP script can handle the above four tasks based on the button that was clicked and executing the appropriate code segment. Therefore, a single form that handles multiple submit task buttons is needed, as well as a form processing code segment that implements automatic responses to different buttons.
I will first give a simple example: a form with a submit button. This will give you a clear understanding of the basic concepts and prepare you for the more complex examples to come. Here is a form:
The following is the quoted content:
Single-button form