>>CLEAR ALL is not 100% secure against cached libs, and CLOSE ALL kills all projects.
>I start everything with
>CLOSE ALL
>CLEAR ALL
>With some backups and sheer Irish luck I got though all this and all is back to normal.
>There were some times, however, when the program was executing code that didn't exist on my hard disk.
>You've explained that it was probably executing some cached code.
>OK. I got that.
>Is there any way to access that cache?

Nothing reliable. If you can run that odd stuff, and if you can manage to get a reference to the object instantiated, you can show in debugger and try to extract from there. Also, one might try to open like MODIFY CLASS xyz of FileStem.vcx, this is, without path. Possibly it opens the cached one.

I doubt it wasn't on your hard disk. Maybe not as a vcx. But it must be a vcx in a app or exe at least. You run an exe or app, close this, miss to clean up and the cached stuff from this exe/app remains. (or a prg, does not matter, the problem is, it is stored inside the app. An exe is nothing then an app with a wrapper.)

Update
If you can identify the app/exe, REFOX will help.