Hi Devon I built the validation system myself using one of the advanced validation patterns listed in the various Cake blogs. The bottom line though was that when validation ran, it checked to see which screen had submitted the information, and only processed validation for that screen (no need to validate data from previous screens as it must be good since it made it to the database/session).
I can't really give you code examples sorry as it was some time ago that I built it and it would take me quite a while to dig it up and work out the various parts. Hope the above is of some use though. If however your problem is complexity in the page causing the users to make mistakes when entering the data, then I would strongly suggest revising the page. Perhaps break it up into more parts, or have a hard think about the layout and words that you use. These things may also contribute. Regards, Langdon > If you could point me at the validation scheme you used it would be > great. The issue here is that there is so much data input required for > the students that I don't want the interface getting in the way with > too much validation. I had validation wall to wall, and on the > walkthrough because of the number of answers required there was a lot > of red flying. Lot's of room for error and lost time for them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
