>It's back. The first time I ran COPYEXE this morning in VFP7 the same slowdown took place - about 25 seconds to process.
>
>My coverage log showed that each COPY FILE cmd took about 2.8 seconds. Somehow that command is getting slowed down in VFP7.

Good! You need reproduction-ability to be able to solve these problems, as a rule. First, one thing I think is evident - you're getting some bad timings because of caching. Once cached, runtimes & code will often run 10 times faster (or so), so such testing is useless. You need a clean cache for meaningful testing.

Second, have you tried it on different machines yet? That may help isolate the problem. Also, alter the code to copy from one DIR on a machine to another on the same machine, to see the performance, and if it's network-related.

I run a COPY FILE EXE that often copies a 4MB EXE from server to local, and it takes no more than 2 seconds over a T1 network. This is in vfp5, 6, and 7. VFP7 appears much faster, but our average machine is faster now, so the vfp copy-speed may not have changed - but it certainly didn't get slower with vfp7. So I can pretty much guarantee that under "good" circumstances, you won't have these delays, whatever the reason for them.