Very Computer

> In my current Win32-proggie I want to copy a file.
> Normaly I do this with CopyFile(src, dst, false), and this works fine
> in the debug-build. The problem is that the Release-Version doesn't
> work properly. The function return successfully with 1, but the file
> isn't copied. Even (if the dst wasn't empty) the dst-file is
> removed!!! So, this can't be a problem with my security-restrictions
> of the account (by the way, I use the root-account!)

> What's the problem? I've read the former postings to this problem but
> they answer the question not specifically!

> If anyone has some remarks...

> > In my current Win32-proggie I want to copy a file.
> > Normaly I do this with CopyFile(src, dst, false), and this works fine
> > in the debug-build. The problem is that the Release-Version doesn't
> > work properly. The function return successfully with 1, but the file
> > isn't copied. Even (if the dst wasn't empty) the dst-file is
> > removed!!! So, this can't be a problem with my security-restrictions
> > of the account (by the way, I use the root-account!)

> > What's the problem? I've read the former postings to this problem but
> > they answer the question not specifically!

> > If anyone has some remarks...

> maybe filenames have not full path and assume certain current directory which
> can be different for debug and release build.
> Output the filenames and working directory before copying with MessageBox or
> write them to a file.
> It can't be a security problem if it works in debug mode.

> In worst case file handle could be destroyed by some code before and don't let
> access files properly anymore.
> But usually it is a problem of wrong file path, use full pathnames for both
> filenames in CopyFile.

> Check the GetLastError code after copy and see what it means.
> 3rd parameter of CopyFile is important to set correctly (allow overwrite if
> existing).