In a perfect [browser] world. I would agree with you, but I have seen browsers do some crazy ace stuff, so I don't trust the "before the form is submitted" as the end all.
My Question is why not check the id first? It is not a whole lot of overhead. I think in the name of data integrity, I always just want to make sure. I worked on a piece of accounting software once. We had to read and write multiple entries for a single process. Once they all finished, then we check them all again. Stuff fails. So, it's better to check. Same with product inventory values... I always check after I write to make sure the totals match, or equal 0 rather. You take it from here, and put it there. The totals of each need to reflect the change. -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
