>>There are dozens of backup products, many of which work with CD-RW or other disk-style removable storage, as well as to tape. There are a couple of ActiveX control based products that can be incorporated into the VFP app to interact with a third-party backup product to handle the backup as well.
>
>That was the direction I was heading.
>

You can command-line drive most of the CD creation software, telling it to reformat the CD, and then use XCOPY (or a better tool) to copy the folder subsystem of interest to the CD if it writes directly to CD-RW, or fire a standard backup job that targets the CD drive. You could remember to change the disk whenever you remembered; if it wasn't blank, it'd have the beginning of the prior week copy of the file system made. With CD-RW, you could use the media in standard backup philosopies, like the typical 20 medium media set backup cycle (5 daily media, the fifth rotating with 4 more for the the end of week media for the prior month, and 11 more rotating end-of-month media, allowing you to go back 5 days within the previous week, 5 weeks for at least the last month, and 12 months for the prior year on a total of 20 CD-RW disks, vs perhaps as many as 265 CD-R disks per year if you didn't use a multi-session CD format to cover the same 5 day week (add 1 more CD-RW in the media set for a 6 day week, or 2 for a 7 day week.)

>> More information about the environment, data volume, and controllability of file access during the backup process would be necessary to address this more adequately.
>
>Files will be released, though I won't code the app to assume that. The environment is a W2K server, NT workstations, ethernet. Data is about 150 MB and that's generous.

Not a problem; at worst, write it in VB and create a VB COM object or ActiveX and fire it from VFP. < g,d&r >