After much troubleshooting with this I finally got it to work. Here's what worked for me:
Background information - I'm creating a simple messageboard app as an ASP.net project for my students. One of the pages in the assignment is a form that allows new members to join the messageboard. The form must check to see if a USERLOGIN already exists and if it does, it needs to reject the form and make the user pick a different USERLOGIN for their account.
Initially I had: Database Connection Database Insert
Next I added a validate data step to check that the USERLOGIN entered into the form does not exist in the database. I added this before the Database Insert step. In my steps panel I ended up with the following steps in the exact order shown: Database Connection Validate Data Database Insert
This did not work. The form still permitted multiple users with the same USERLOGIN.
I was going to try scrapping the whole form and try starting over but decided to try removing all of my action steps and trying again. I added a database connection. Then I added the Validate data step. Next I right clicked on the Validate data step and added the Database Insert step.
By doing it this way it worked - if a user entered a USERLOGIN that already was in the database it rejected the form input as it was supposed to.
It probably shouldn't make any difference when the Validate Data step gets added as long as it is before the Database Insert step, but apparently it matters what order you create the steps.
Teodor, any idea why this is the case? Or is it possible that something was left behind after the recent extension updates that was causing my problem?
Hello Scott, It does not matter how do you add the insert step. The only thing you need to make sure is it is after the validate step. Everything after the validate step, when the validate is false, won't be executed. Probably some old files were left there, on your server.