Hi i am hoping someone can:
[list=]Configure the file upload on my form, i have three areas on the form that needs files uploaded[/list]
[list=]add a back button to my form, i wish to allow the content to remain on the form and the back button allow the submitter to go back over answers with out loosing the data imputed.[/list]
[list=]also allow the customer to save the data and come back to the form at a later date to finish filling in the form[/list]
many thanks
Nichola
Hi Nichola,
All of these are possible - by all means PM me the site URL, the form name, and a SuperAdmin login and I'll take a quick look to see what is involved.
Bob
Hi Nichola,
Sorry to be a while getting back to you. I've had a quick look at your form this afternoon. I think it is the longest form that I have seen for quite a while.
Here are some comments.
The Files Upload action looks OK but is in the wrong place. It needs to be in the event which the page with file elements submits to. i.e. the Files Upload action for the logo and contract elements on Page 2 needs to be in the On Page 3 event; similarly the Files Upload action for the price list element on page 5 should be in the On Page 3 event.
In both cases the Files Upload event should be before the Multi Page element so that the file info is available to be saved.
I notice that you seem to have a lot of Handle Arrays elements in the form most of which aren't doing anything - you might want to clean those up. One per event is enough if there is array data being submitted like a CheckBox Group or a multi-select Drop-down.
In the On Submit event the DB Save needs to be after the Multi Page action so that the data you want to save is available - at present, only the last page's data is there.
You also don't need the HTML (Render Form) action in that last On Submit event as there is nothing to render at that time.
It's up to you but I prefer to add a DB Save after each page submit with a form like this as that makes sure there is a secure copy if the User session times out - otherwise the data may be lost.
To make this work you need an identifier in the record - that could be the record primary key, or a unique string, or a user id if there is only one record per user - that is passed forward to the next page in a hidden input so that the same record is updated each time.
I would also add a 'status' column to the table so that you can tell if the record has been finally submitted and should therefore be 'locked' or can still be edited.
Bob
Hi Bob,
Thanks for your reply, are you able to quote me to do this work.
Also the form has stopped saving new information! This maybe a web server issue!
many thanks Nichola
(ps my reply has taken longer than expected because i was getting security alerts for malware from your forum.)