Form Submittion

Hi All,

I have a form that people can fill in but I wish, once they press submit, for them to be taken to a page that displays the fields and the data they placed against it.
Then a submit button that posts to my DB (already have) and an edit button where they can go back and modify what is incorrect before submitting again.

Welcome to the forum. Please see ManiacDan's New User Guide to learn how to post a question that will produce useful help.

Hi,
What more information would you like me to provide?
I was under the impression that I have supplied enough information to produce a useful answer?

I think what gw1500se is trying to ask is "What is the actual problem" or "where are you stuck"? You've simply provided a "I wish for..." which is great and we're all behind you in achieveing that but other then that, you don't say what the problem is preventing this wish coming true or what you've tried so far (if anything).

And if you had read the link, you would have understood why what you presented is not enough.

Oh ok, well the problem is I do not really have any idea where to start.

I have my table set up in MySQL DB, I have the form working fine. When I click submit currently it places the info into the DB and tells me that it has been submitted.

However I want to add the middle man, but showing the user what they have entered before submitting this information to the DB

May I suggest that if you have the 'write to DB' bit working then you keep it like that but on the confirmation screen, simply re-create the form and set the "values" of the HTML elements to the values submitted by the user.

For example, in this confirmation screen below, the user submits their name using HTTP POST ... I'll skip the write to DB bit but what we need to do sanitise their input using HTMLENTITIES and then write that back to screen ...



That's just a rough idea but hopefully will set you off in the right direction

I hadn't thought about doing it this way really, I don't really want duplicates in the DB and also on submit it produces an email which I would not want them getting many emails for the same form

Well, it was just a suggestion, you can of course, use that code above BEFORE it updates the DB and only have it update on their next click of the 'submit' button.

Oh, by the way, this method I suggested wouldn't end up with duplicates, at the point of displaying the form it's INSERTed the record and you can get the unique ID that is returned from the INSERT statement and use that in a hidden field.

It's up to you of course, as long as you make it clear to the user that "AT THIS POINT, YOUR DATA HAS NOT BEEN SAVED" then do it however you like but don't ever forget how dim users can be - even with a 72pt bold, flashing, red on yellow banner, it'll be ignored by them and they'll be left wondering why, when they closed the browser at that point, they have to re-do the entire form.


EDIT > With regards to the 'Thanks for submitting your data' email, only do that AFTER the data has been written to the DB, if the user then EDITS their submission, you don't need to re-send it (as you'll know if you're doing an INSERT or an UPDATE)

Alternatively you can define a column or combination of columns as unique and update the database on the first submit. There would need to be some way to connect that column with the user (perhaps a username) to prevent inserting a duplicate record. Then after editing, do an update rather than an insert using that value in your where clause.

One final method is to manage all the editing on the client via javascript and then the submit would only need to be done once.

This sounds like a wonderful solution then I will attempt to put this into action tomorrow and let you know how it goes Thanks!!