If you don't need them to be relational, a good way to store them is in XML files. It would be fairly easy to write a generic cfc that would take the transaction information and create/append an xml file to store the transaction. These XML files could be used to display transactions or roll them back as needed.
BTW, you are updating tables, not forms. Forms just allow access to data. -Sam Curren --- [email protected] wrote: > We have a need to track Form Updates by users i.e. history of updates to > Forms. > Once the user submits a from after validation, we want to track the updates > done. > e.g. > User A can change their Credit card info several times on a Form, we need to > Track those changes > and any other agreements they might have agreed to on the Form. > > Options. > 1. Save the entire contents of the Form as *.htm/*.pdf files or populate > them in the DB. > 2. Implement a complex DB Relational Structure to store the content and > data. > > Any other Ideas? Anybody else implemented something like this before? > > Thanks, > Joe Eugene > > ---------------------------------------------------------- > You are subscribed to cfcdev. To unsubscribe, send an email > to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' > in the message of the email. > > CFCDev is run by CFCZone (www.cfczone.org) and supported > by Mindtool, Corporation (www.mindtool.com). > > An archive of the CFCDev list is available at www.mail-archive.com/[email protected] > ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
