thats what i do. on the edit page loading, i set the original values into hidden fields, and then sense a change, if there is any change, i write all the new values to the database.
tw On 5/25/06, Dave Francis <[EMAIL PROTECTED]> wrote: > Or you can keep the original values in hidden fields, and compare them > against the input fields when they submit. Saves a db access. > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 25, 2006 1:28 PM > To: CF-Talk > Subject: RE: Tracking changes to a database > > I had the same issue with a form I was having people fill out with pre > entered data. > > The logic after I filled out the form was that I would check each entry > against the current data. If it was different, I would put it into a > "Changelog" table. > > Then I would do an update. > > Original Message: > ----------------- > From: Les Irvin [EMAIL PROTECTED] > Date: Thu, 25 May 2006 10:42:24 -0600 > To: [email protected] > Subject: Tracking changes to a database > > > What's the preferred concept in tracking database changes? > > For example, let's say there are 3 fields in a database. A user can go in > and edit one, two, three, or none of the fields. How can I track what was > changed and what was not? > > Thanks in advance, > Les > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:241494 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
