Hey guys?
I have created a form with chronoforms which is capable of validating fields (dates, blank fields, etc) as one enters information in them before it can be submitted and added to the database.
I wanted to know if there is a way I can prevent a user from resubmitting the same form once it has been added to the database.
As in, before a form is submitted, is it possible for the system to check if a certain key field is already in the database and then inform the user as such hence preventing such an action??
I Hope am clear.
How do I go about this??
Am using Joomla v1.5.15 and ChronoForms v3.1 RC5.1.
Thanks.
I have created a form with chronoforms which is capable of validating fields (dates, blank fields, etc) as one enters information in them before it can be submitted and added to the database.
I wanted to know if there is a way I can prevent a user from resubmitting the same form once it has been added to the database.
As in, before a form is submitted, is it possible for the system to check if a certain key field is already in the database and then inform the user as such hence preventing such an action??
I Hope am clear.
How do I go about this??
Am using Joomla v1.5.15 and ChronoForms v3.1 RC5.1.
Thanks.
Hi rading,
It's certainly possible - just how depends on what you are checking. How will you know that they have already submitted? What is the test?
Bob
It's certainly possible - just how depends on what you are checking. How will you know that they have already submitted? What is the test?
Bob
Thanks for replying Bob.
Well, I think its better I told you what the form does. The form is a fee payment form where a user fills in details of the payee as well as information about his payment options. These could be the cheque number, or a bank slip number, etc, but only one payment option can be chosen at a time.
Whichever payment option is chosen, a unique number which identifies that payment option (either a cheque or a bank slip) is filled after selecting the payment option. I have called this field cheque_no, so I guess the check has to be made against this field. That way if the user forgets whether or not a payment has been recorded, it can prevent it from being submitted again.
Well, I think its better I told you what the form does. The form is a fee payment form where a user fills in details of the payee as well as information about his payment options. These could be the cheque number, or a bank slip number, etc, but only one payment option can be chosen at a time.
Whichever payment option is chosen, a unique number which identifies that payment option (either a cheque or a bank slip) is filled after selecting the payment option. I have called this field cheque_no, so I guess the check has to be made against this field. That way if the user forgets whether or not a payment has been recorded, it can prevent it from being submitted again.
This topic is locked and no more replies can be posted.