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

Yeah it is on OS call. However, I misunderstood the nature of the problem. I'd say that this is something that VFP should correctly report. I'd recommend that you fill out a bug report on the MS site.

>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?

Nope, you can't necessarily. For example, a printer error won't be returned. In some instances, system errors such as this can, and should be caught. However, in those cases where Windows has a mechanism for reporting the error to the user, such as printing errors, you probably won't get an error message.