Thanks for all of your help the other day. I'm now amending my processes to have validation take place on the same page as the original form and, in the main, it's working fine.
However - I have a registration process that involves:
1. validation of form entries. then, if validation passes:
2. checking for a duplicate record (generate a recordset - checkDuplicates - based on email address). Then, if validation passed and no duplicate records:
3. insert the new record into the database. Then,
4.send a confirmation email back to the user as well as an email to the site admin to advise of a new record added
I can successfully trigger the final, insert record behavior based on whether the checkDuplicates recordset is empty or not but NOT on the passing of the validation process so, if the email field from the registration form is correct (a valid email address) but there are errors in other fields that get caught by the validation process, the insert record behavior still triggers and inserts data even though the validation process has bounced the user back to the original form with errors noted for correction. This could (and does!) result in multiple entries.
Whilst I could hand code an big IF statement to say that if the checkDuplicates record is empty and each of the form fields are not empty, THEN insert the new record but it would be far easier to trigger the insert record behavior if validation is successful. Am I missing something here - as that option doesn't seem to be available.
I used to handle this process successfully in a multi-stage process prior to having the recent issues with Win 8, DWCS4 and the WA extensions that we managed to solve the other day - but now, as Form Validation wont allow me to access the validated entries across to a second page, I'm having to run things as above.