>Wow! This thread sure has a bunch of complicated ways just to do a backup.
>
>I solved this problem in a simple way. Hmm. Maybe I missed something...
>
>The way I do it is like this
>
>1. I create a subdirectory under the directory my main executable is in called DATASTRU. Here I store a clean empty copy of my database (.dbc, .dct, .dcx) and tables (.dbf, .fpt, .cdx)
>
>2. When the user selects BACKUP DATA from the menu, I allow them to select a backup directory that isn't one that contains current live data or data structures.
>
>3. I then copy the whole DATASTRU directory to the selected backup directory.
>
>4. I then close each table that I want to backup, use the corresponding table in the backup directory, and then append from the original.
>
>5. During the copy I play a little AVI file, FILECOPY.AVI (i.e. the same as the old blinking "WORKING" misguidance of the old DOS days) :)
>
>6. I then close the backup tables, reopen the originals and reset any other needed information.
>
>The result is that a user who is set up in my program to do backups can initiate a backup of live data ANYTIME regardless of if ANYONE is currently in the system.
>
>So far this seems to work great and I haven't had any problems with it.
>If anyone sees a hole in this method please let me know.

---

I like the WinZip or DynaZip option myself. Gets open tables, the dbc and jsut about everythig else in the path I state! Open files are an issue of the past for me too!

__Stephen