Newsgroups : Borland : borland.public.delphi.nativeapi.win32 : 2007 Aug : Proper programming practice: MoveFileEx
| Subject: | Proper programming practice: MoveFileEx |
| Posted by: | "Loren Pechtel" (lorenpechtel@hotmail.invalid.com) |
| Date: | Sun, 12 Aug 2007 09:30:21 |
I've been having a bit of a dispute with tech support for a program.
They consider my Novell server to not correctly implement the Windows
API and cause a function to fail.
As far as I can tell the real issue is a bug in their code where they
left a file open before calling MoveFileEx. This works under Windows,
it fails if the file is on a Novell server.
Assuming my diagnosis is right (and I find it hard to believe it's
anything else--the file is written to the server in a temp location
and then the attempt to rename it to it's target location fails
because somebody else is accessing the file--except the target doesn't
even exist, it can't be locked. All that can be locked is the temp
file that it just created.) is it Novell's fault or their fault?