I am now implementing in my base BIZ class saving to audit trail table for all transactions

One thing (and admittedly, I'm so far removed from FoxPro that I don't even remember if Fox databases have triggers)....if you can do this in the database with triggers, you're better off.

Logging should be a function of the database, not the application. It may seem like a good idea to implement logging in your application code - but any data changes that occur outside your code won't get logged. Though people want to say otherwise, the truth is that changes occur outside the application.

That's the beauty of triggers or even Change Data Capture in SQL 2008 - you put them in the database and they're like "Big Brother" - they see everything.

But if Fox doesn't have DB triggers, then you either have to put the logic in your application code, or look for a 3rd party solution, or maybe someone else who is working with Fox has another idea.....