[BCB] Win32 API function MoveFileEx

["Mike Louden" <the.duck@nospam.btree.com>]

I seem to recall using this command successfully on NT but can not swear to
it.

I doubt it is an error of Borlands since I beleive they just pass the calls
straight through.

I think you should update with the service packs since I do know that new
API commands came out
in later service packs.

-- Mike
----- Original Message -----
From: Jim Dodd <jim_dodd@nospam.onsetcomp.com>
To: <bcb-list@nospam.orionlink.net>
Sent: Tuesday, April 27, 1999 3:09 PM
Subject: [BCB] Win32 API function MoveFileEx


> I am trying to use the Win32 function MoveFileEx() in a BCB3 application.
> I want to use this function rather than the simpler MoveFile() because
> MoveFile() does not let you move a file to a different volume.
> MoveFileEx() does allow this. Unfortunately, when I execute MoveFileEx(),
> I get an error #120 which means that this function can only be used in
> Win32 mode! Well, I'm running this on Windows 95.  The simpler MoveFile()
> does not return this error. I don't have Windows 98 nor Windows NT to try
> this on.
>
> Has anyone else seen this behavior? Is this a bug in Borland's interface
> to the Win32 libraries or a bug in the MS Win32 library? I only have the
> original version of Windows 95 and not SR1 or SR2 installed. Perhaps this
> is the problem.
>
> Eventually, I will use the more capable SHFileOperation() function ( if
> I'm allowed <g> ) but for quick and dirty work, MoveFileEx would be easier
> to deal with.
>
> Jim Dodd
> Onset Computer Corp.
> jim_dodd@nospam.onsetcomp.com