For 1, 2 and 3, you will typically enter records into the database during the login process and the logout process that you create.
You will need to put something in onSessionEnd for when sessions expire just in case they don't use your logout portion of the code. As for the data changes, I would recommend letting the DB handle this for you. Most modern databases have triggers. Use triggers to copy the record that was changed or edited into a duplicate log table or log database. I tend to create a copy of the entire schema into a database seperately. Example, CircusDB and CircusDB_Log. The exact same table exist in each and copying data from one DB to another on the same server is a trivial overhead. Teddy On 1/16/07, Les Mizzell <[EMAIL PROTECTED]> wrote: > > Client want a complete log of *everything* that happens to within CF > database admin system > > No problem: > 1. Who logged in > 2. When they logged in > 3. When they logged out > 4. If they changed/added anything > > Problem: > 2. EXACTLY what they changed/added > > This is a fairly large multi-page application consisting of 7 pages of > long forms. They didn't mention this until *after* I completed everything. > > What's "best practice" here to keep up with this? > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:266680 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
