Thanks, everyone for your comments.

Mark, I've got Duffy's code (from his Advisor article) diligently filling in cWho and tWhen in my DBC, as well as PK generation. I've got a request in to purchase the rest of FoxAudit for the rollback capabilities it offers.

I think the original newsgroup question was related to not wanting the user to even SEE the data so they would need to do something with encryption, go the COM route, wait for VFP7 or move to an SQL database.



>You got some good detailed replies to this already, but I want to comment on this in general.
>
>Generally, whatever rights you have assigned via the OS, the user will have regardless of the front-end. This is why I use as many database features as possible. These include triggers, default values, constraints and stored procedures. This way, my data integrity is independent of the front end [user] accessing the data.
>
>I use Insert, Update and Delete triggers extensively. My insert triggers in Oracle populate PKs using sequences and other key fields such as Updated_By and Last_Update date. My update triggers also update the Updated_By and Last_Update fields.
>
>If my backend is VFP, I use the similar features of the DBC.
>
>No matter what you do, there will always be at least 1 user who want to access the raw data. So, it pays to put in the effort on the back-end. When you do, the front-end development, if you have a decent framework, is almost mindless. :) See ya at DevCon!