Hi,

Many thanks for the contributions.

Evan's understanding of our application is correct ... except that it is the recovery time that is critical to us. We need to be back into a consistent state (from a business perspective) well within 15 minutes of any failure of any kind and with minimum loss of data. Hence, if our backup works, we can replace the database at a known "good" time and replay the transactions (which are in fact EDI messages) that happened since that time.

Our application started off as a Fox 2.5 on one PC and has grown into a mission critical multi-user system. We have not had the luxury of designing for this requirement from scratch ... hence our "quick and dirty" approach of backing up the whole database rather than doing transaction logging. (I guess we will be able to do it properly one day).

However, in the meantime we just want a totally fool proof way of doing this backup to a local and or remote machine whilst the users are working. We are now using "COPY TO" and that seems to be working fine.

Regards

Richard Schneller