If you just want to *see* the data and don't want to be able to extract it back out again you can use a more obtuse approach and store the submitted form data in a long text field, via cfdump if your needs (and data qty)(are very simple and via a loop and table row construct if more complex. You'll need a table that tracks the User's ID number as a separate field, as well as a date and time of mod.
I usually log the entire submitted form scope minus a few key things like submitted passwords, the fieldnames field, the submit button name or anything else I don't want stored in the clear in a db (uh... like a cc number). You can fancy this up by encrypting data as well. On Tue, 28 Dec 2004 10:37:18 -0500, Claude Schneegans <[EMAIL PROTECTED]> wrote: > >>Implement a complex DB Relational Structure to store the content and > data. > > This should not be that complex: just design a table with > - user ID > - date-time > - name of table modified > - name of column modified > - modified value > > -- > _______________________________________ > REUSE CODE! Use custom tags; > See http://www.contentbox.com/claude/customtags/tagstore.cfm > (Please send any spam to this address: [EMAIL PROTECTED]) > Thanks. > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Gold Sponsor - CFHosting.net http://www.cfhosting.net Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188887 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
