>No, I didn't change anything - my error routine already records the current path setting and it tries to verify that the file causing the error exists (or not). In this case, however, I'm not getting an error file.
>
>But, we may be going somewhat afield here. A typical scenario is:
>1. An error of some sort exists and gets passed thru the chain to the global error handler (I have yet to find out what that error is).
>2. The handler calls aStackInfo() to get the program hierarchy.
>3. VFP crashes with Suspend, Cancel, etc. buttons with the message "File not found" where the file name is an FXP name.
>4. That file's name and path are OK -- only the drive letter is different on the client's system.
>5. VFP is, by now, catatonic. If I "suspend" and debug, it's useless.
>
>I'm presuming that, as the drive it displays is from my development system, it could only get that from within the FXP file itself (it's embedded there as a PRG and path). But, why would VFP read that embedded filename? I don't know but I presume there's a good reason. OK, but then, why does it tell me that that file doesn't exist? If it doesn't exist, how could it have read the embedded filename in the first place? Where else could it get a nonexistent drive from?

For many of your questions if not for all, the answers could be found if you know the line of code where the error occurs, and the nature of error documented in your custom onnerror routine. But (as far as I understand) your onerror routine does not work in this case, and the code line is unknown.

Probably you are using some subclasses of the VFP classes where the internal onerror routine exists. Probably you used VFP wizards to create some of the controls, like buttons on forms, etc. Most of them contain internal onerror routine that may display error messages with options Suspend, Ignore, Cancel.

If it is the case, then you need to dig into the code of VFP class to see exactly what it is doing and how.

Good Luck