George,

Of course it's a bug. This is the venerable xBase COPY, not an OS command.

The bug does not happen if you open table MyTable in VFP session 1, then try to write another table onto it in VFP session 2. This is caught, as it should be. It is only when the table is open within the same session that the error is not caught.

And if it were a system error, surely I can expect fox to report system errors to me?


>Kenneth,
>
>This is neither a VFP "bug" nor "feature". The fact that VFP doesn't catach it is caused by the fact that VFP can't catch it. The copy command is a function of the operating system (Windows). Even Windows doesn't know if a particular file is in use by someone else prior to attempting the copy.

> That's why an error occurs on the system level, not the VFP level.