Just so my previous email doesn't get drowned out in a debate over ajax, if I were tackling this problem, I would have a hidden form field on each page that lists the fields that have been changed. Attach an onChange handler to each form field that the sys managers can change. Have it call a function that simply adds the id of that form field to the hidden form field. On the form submit, just look go through the list of changed fields and log the before and after data. Quick and dirty and requires minimal change to your existing setup.
Judah Les Mizzell wrote: > > I feel it's ridiculous to track changes to fields BEFORE the > complete data >> set (form) is submitted, unless that is a specific intention of the business >> logic, which I don't think in this case it is. > > Basically, ADMIN sends an email to all the sys managers that have > systems listed in the database. The sys managers have 20 days from the > time the email notice is sent to complete their information. After that > they're automatically locked out. > > ADMIN logs in and can see all the data in the current record for each > sys manager, but also needs to see a log of the changes each sys manager > made each session over the 20 day period. > > The entire project is finished using pretty much standard CF code for > multi-page forms (or my weird version of it anyway) - they requested the > "change log" after the fact. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2. Free Trial http://www.adobe.com/products/coldfusion/flex2/ Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:270389 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
