Also, as part of the validation above, the field can not be empty.
I keep thinking there should be a better way but don't have an IWP set up to test.
I suppose you could set up a group of global fields for data entry and when the user submits the data, use a script to copy the data into the correct fields if they pass validation. Then canceling the data entry is simply a matter of clearing the global fields...
Hi Phil thanks again. While this approach sounds very sound, it also sounds very labor intensive especially if portals are involved. Is there another approach?
Well that's why I keep thinking there should be a better way :-(
But since I don't have a DB set up as an IWP system to test, I'm limited to tossing out general suggestions for you to test.
What if you put a "Submit" button on your layout that used a script to confirm valid data in each field and then used commit record to submit the changes only if they all passed validation? You could at least use a loop to validate the portal records that way...
Thanks for the new approach. It diffinately has opened my mind to think in new directions. I looked through the functions and script steps. Unless I missed a function or 2, I believe that inorder to do this, I would have to recreate the validation in code for each field with validation and compare the new value to it before commiting a record. While this approach does seem much less labor intensive, it still seems a little like we are taking the instant out of instant web publishing.
I am going to see if I can restructure things a bit in the portal so that the strict validation will not be necessary there.
However, I'm sure I will be using a lot of what you told me at a later date.