>>Hi,
>>
>>I was wondering what others here think about storing changes to every record into some kind of audit trail table? Is this a good and reasonable design or waste of database storage?
>>
>>TIA.
>
>Depends on business requirements. I put it in place, but have switches to turn it on or off: edits, deletes, additions, etc....
My business requirements are pretty much mine (since I sell vertical market app, not custom application). But once in a while I find myself having to answer to a customer as to "do you know who changed this record and how?" So I decided to tackle this by adding to my base BIZ class a feature that automatically stores any change to every record. The record is stored in a memo field (varchar(max) in SQL server) as a XML string created with cursortoxml(). I am less concerned with the storage that this data takes in SQL Server. But in VFP this could be noticeable. At least, based on your reply, I see I am not unique in this approach. Thank you very much.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
