I haven't been following this thread very closely, so please forgive
me if this has already been considered. I assume the problem is that
the backup algorithm creates a directory to contain the backup, so if
the location of the backup is in the database it tries to copy the
contents of the backup into itself.
Would it work to make a list of the contents of the database before
creating the backup directory, and then make the algorithm work off
the list? I suppose it would be better to keep the user from putting
the backup in the database, but that isn't always easy to prevent.
- Jeff Lichtman
[EMAIL PROTECTED]
Check out Swazoo Koolak's Web Jukebox at
http://swazoo.com/
