Ted Roche wrote on 2016-01-20:
This only apply to a compiled EXE, and not the development environment,
right?
I'm not sure what sort of suggestions would be helpful.
How about including a small FoxUser.DBF, embedded inside your executable. VFP *should* open it read only.
Or, of course, include a CONFIG.FPW with RESOURCE=OFF.
Ted,
Thank you. I just included the foxuser.dbf in the EXE. The EXE is in a folder without the foxuser.dbf, and I still get the same results with Cancel and Ignore.
Just for grins, I set the resource=on and recompiled. I get the same results even with the table included.
Then I set resource=foxuser.dbf and got --------------------------- Microsoft Visual FoxPro --------------------------- Visual FoxPro cannot start. Insufficient Memory. --------------------------- OK ---------------------------
Thank you for helping.
Tracy Pearson PowerChurch Software