At 06:48 AM 29/06/2006, you wrote:

>We use .FBK as our backup file extension and we have one customer who
>when he runs his backup task, the backup happens but it fails to
>overwrite the daily backup file. If we rename the existing backup file,
>it will create it, but it won't overwrite it. We noticed that he had
>installed some family tree software that was associating the FBK file
>extension with it's software. We tried removing the association of the
>.FBK files but it didn't help. Has anyone else every experienced
>something like this?

It is "as designed" - you cannot overwrite a backup file; or,
rather, you cannot output a backup to a file that already exists in
the target location with the same name. Think for a moment about the
implications if it was allowed...

./heLen