Hi Barry,

As long as you just want to access for analysis how about this.

Modified from help:

LOCAL lcOldOnError

* Save the original error handler
lcOldOnError = ON("ERROR")

* Issue ON ERROR with the name of a procedure
ON ERROR DO errhandler WITH ERROR(), MESSAGE()

* code to which the error handling routine applies
USE TableThatHasTheSameStructure
APPEND FROM TableThatHasAProblem

* Reset the original error handler
ON ERROR &lcOldOnError

PROCEDURE errhandler
LOCAL aErrInfo[1]
AERROR(aErrInfo)
RETURN  && Ignore the error?????

* It would probably be best to make sure
* that it was a function not found that 
* caused the error, though.

*DO CASE
*   CASE aErrInfo[1] = 1 && File Does Not Exist
*      * display an appropriate message
*      * and take some action to fix the problem.
*   OTHERWISE
*      * display a generic message, maybe
*      * send high priority mail to an administrator
*ENDPROC

>hi mike
>i didn't know about the incompatibility. i tried the append from thanks with the same errors. it seems as though this is something i'll have to live with.
>i'm analysing only. it's a shame because it means i can't really use vfp to create my analysis tool due to the 5 errors (there are 5 tags with the problem) that the user will receive on opening the table. doesn't look too professional!
>thanks for your help anyway...