>I am looking to create a change table for my program so that when data is changed I can capture who, what and when the data was changed. Is there somewhere I can look to get ideas on how something like this is done. A couple of ideas come to mind, a single seperate table that will store table name, field name, old value, datetime change was made and who made it, but I can see this table growing very large in a busy environment. The other way is to create a change table for every active table in the database to store about the same info, but that would make a large number of tables if the database has a large number of active tables.
>
>What is the best way and is there a demo that I may look at for other ideas?
>
>Thanks
>Ron Olds

A single table would be easier to maintain, IMO. If it grows too large, copy its contents to a "historical" table, perhaps separated by month or so.

With 10-15 users, ca. 70 tables, I got historical data of 200-300 MB, in ca. 2 years (I use a single audit table). Much more than all the other tables together, but still way below the VFP limit of 2 GB.

I still find it convenient to copy to a historical table (and clean up the main audit table), to reduce the size of the regular backups.