>>>I am looking for suggestions on backup procedures to include in an application. Ideally, it would need to include compression and flexibility regarding files to backup and where they will be backed up to.
>>>
>>>Thanks in advance.
>>
>>I use DynaZip. Works great with VFP and comes with sample VFP code to get you started. Just remember that open files will not be able to be included in this kind of backup [and most other backup methods as well].
>
> One way to get around the open file problem is to create a function that will SELECT * FROM all your tables to a backup area. Then you can zip the resulting tables. This way you never have to worry about the file being open.
>

If you want all the CDXs as well as DBFs, you could also use a scheme which loops through the Tables doing COPY TO ... WITH CDX.

Just out of curiosity, does anyone know if there's a significant performance difference between SELECT * and COPY TO (without CDX) if you're returning all records (or all non-deleted) records from the tables? (Assuming both commands are fully Rushmore optimized, but does Rushmore come into play if you're returning all records anyway? Obviously it comes into play if you're excluding deleted records.)

Cheers,