Folks,

I lost a half-hour or so today before determining that Visual Foxpro is failing to trap a certain error. Specifically, if you attempt to copy file1 to file2, while file2 is open, the user gets the error, not the error trapper.

Following is code to reproduce. Does anyone else get the same result?

Special: Two points to the person who comes up with the most creative doublespeak explaining why this is not a bug, but a feature.

CODE BEGINS HERE:

*
*  FAILED ON ERROR COMMAND
*  by Kenneth Downs
*  ken.downs@msginet.com
*
CLOSE ALL

*  Get a table open under
*  an alias different from
*  its Stem
*
CREATE TABLE NoError1 (Field1 C(5))
USE
USE NoError1 ALIAS IAmNoError1

*  Get another table open
*  
SELE 0
CREATE TABLE NoError2 (Field1 C(5))

*  Create a simple flag that
*  will go to -1 if the
*  command fails on an error
*
LOCAL lnError,lcError
lcError = ON("ERROR")
ON ERROR lnError = -1
lnError = 0

*  Attempt to copy the 2nd table
*  to the first, triggering
*  an error, which does NOT
*  get triggered
*
SELE NoError2
COPY TO NoError1