I have been experiencing a problem with the Resource Memo file being erased when building or running an APP or EXE where the Debug Info is excluded. I believe it has to do with a call in an Application Class to open to set the resource file when running the APP from the IDE. I choose to set Resources off in a distributed EXE, as we use a framework with built in position memory, but I want Resource set on while testing to preserve my debugger setup.

It is a real nuisance when the FPT is erased, and I have resorted to keeping a recent copy in VSS so I can quickly restore. I loose any new stuff, but that is better than starting over all the time.

When it happened a few days ago, I restored, but after doing so, the resource file stopped working, and the command window was no longer reading the _Command.Prg history. I ZAPPPED the Resource file so it would have to rebuild, and it has. I also cleard the _command.prg, and tried copying a file form another project, But I still don’t have any command history.

I have been setting the resource file on the fly as a project opens to a local project file, which also performs some housekeeping to minimize Resource file induced fatal crashes:

SET RESO OFF
SET RESO TO (local project file)
USE SYS(2005) EXCL
PACK
PACK MEMO
USE
SET RESO ON

There is some error handling included, but this is the operative code.

I have reluctantly switched back to using the default resource file, although it is not named "FOXUSER" or located in the "Documents and Settings" folder hierarchy by removing the second line of the code, and accepting the default file name which is stored in the Registry. Still no command history.

I am aware that the _Command.Prg is supposed to be read form the same path as the RESO file as VFP open, and written back to that file when VFP closes. It is not happening, and I don't have a clue. Can anyone offer a suggestion?