>Al,
>
>Thanks for the input. I created a procedure that worked pretty well when used in the development (VFP.exe) environment, but when used with runtime EXE it did not perform well. Instead of MESSAGE(1) returning information about the code line, it returned the "DO EXE_Filename.exe" string. My guess is that this may be acting this way since it can't go to the actual code line to use it.
>
>Your solution could work, but I am not sure that I want that much code effort put into each call to a network file. Could there be some other way??

There always is :-) Seriously, with this technique you add one line of code just before each table open - that's pretty lightweight. Even better, you could create a function that opens your tables for you and put it in there.

The issue is, that by the time your error handler is called, an error has occurred, and the error handler is pretty much on its own. If you're macro expanding you don't have the file name in the source, so you need to get it to a place your handler can read it, somehow.