Like vincent said, it depends on what you really want to do.
I created something similar, it may seem a little redundant but it has its advantages as well:
1) Dynamically populate a table with db info. Each table row was a brief summary of the db entry.
2) Next to each row was an image submit button or link that passed the record id to a review page. If you use a button, like vincent said, each row must be its own form. If you use link you can code something like: <a href='review.php?record_id=$record_id> <img src='blah.gif'> </a>, this would pass your var to the next page.
3) The review page showed the all info regarding that entry (done thru a query like you did, kinda).
4) I provided a edit button that again passed the record id to another page (edit page). Also a delete option, which set off onto another series of fail-safes and such.
5) This edit page pulled all the data reqarding record into form fields where they could be edited.
6) After clicking submit, the new variables are passed to a review page to make sure these where the values I wanted to update BEFORE committing the changes to the database.
7) Finally, after committing the updates, a redirect back to the main listing.
I hope this was helpful.