We have been using FoxAudit for quite a while. However there are a few minor bugs: e.g. roll back and forward is done by time instead of index number - think of different dates on different network PCs, the data delimiter can make problems with binary fields, date handling can make problems: e.g. data input is allowed for year 0000 to 0099 but DATE() doesn't support it that's rather a MS VFP problem. It comes with source code and for this reason you can easily make it work in your environment.

We use it successfully for incremental backups which we retrieve at a different site and apply them to old backups.

To use it you need a proper unique key for all tables. We added an AutoInc-key to a lot of tables. This works great. However the log file isn't readable for humans in contrast to using e.g. an order id as a primary key. Actually you can decide this for each table.

Regarding speed you should avoid writing a lot of records at a time. It is a big difference if you write 1000 records with or without logging (times x 3 or even longer). Normally there is some room for optimizing the application here. If you create a cursor from an existing table bear in mind that the cursor gets the FoxAudit triggers from the table. Those should be removed before you populate the cursor.

Keep in mind that the log tables are sensible to get corrupted if e.g. there is a power failure or user simply switch off. 50% of index corruption is in the log files since we started with FoxAudit. You need to make sure that users still can log in if the log file is corrupted and I recomend that you make available a third party tool like Stonefield Database Toolkit to offer repair tools.

It also makes sense to create a global variable to switch logging off or on for maintenance purposes. Depending on the variable you can return from the stored procedure foxaudit without logging.

Andreas


>We're facing the urgent need of a tool that can track any change made to any table in our VFP database application for production tracking. some points you should know if that, there are some tables which are quite big, like for example one with 1,4GB or so.
>
>now what i am looking for is a tool that can add changes auditing to my databases with the minor effort in programmming, looking for something that doesn't impact that much in performance.
>
>what i am not looking for is advice in how to reduce those big tables, or how to improve our aplications code, at least not in this thread.
>
>I've being thinking about FoxAudit from TakeNote. but in the site they doesn't give much information
>also i haven't being able to get any comments or rating about this product. so i wonder if somebody of you is using this tool and any feedback about it.
>
>is there any other tool to achive this?
>
>TIA