>>>I have an application that moves files from an LAN to the local drive of a client PC. I use COPY FILE to do the actual copying. I'm moving a lot of files in each session.
>>>
>>>This app works great on a Win95 client, but I'm having trouble on a W2K client. Really small files transfer fine. File in the range of 1-2MB move so slowly the process almost seems to hang. It might take 3-4 minutes to move a 1-2MB file. The same files copy in seconds on the Win95 client.
>>>
>>
>>If there are a number of files involved, you might consider using SHFileOperation() to do this rather than the native COPY FILE command - see the Win32 API section for details.
>
>Or the Shell.Application object?

I was thinking in terms of SHFileOperation() from the standpoint of performing asynchronous copies of lists of files through a single operation, with the display of the Windows File Copy animation; certainly, Shell.Application, or, better yet, Scripting.FileSystemObject, might yield benefits, as might spawning a separate task to perform the copy operations in background.