Kevin,

It sounds like a difference between the SET environment between the VFP design time and runtime. Each SET has a default value, those are in effect when the runtime starts. Design time gets it's SETs from the Tools, Options menu settings.

The EXE can not fire up the debugger about the best you can do is have an ON ERROR and Error() methods that log error information to a file. You can use DISP MEMORY LIKE * TO FILE MEMO.TXT to get a dump of all the memvars with their values.

>Folks,
>
>I'm having a problem where I can create an EXE and run it in the VFP command window and it works fine. If I go out to Explorer and double click on the same EXE I get an error (a data type mismatch). I can see the line number where it says it errored out, but I've checked the data that it's trying to read and the data type is consistent with the variable that line is trying to compare (two date fields).
>
>I've tried to debug it by opening DEBUG and DOing the EXE and stepping through it right from the very beginning, but then it works fine.
>
>Is there some method of debugging step-by-step a VFP EXE OUTSIDE of VFP, itself? This is very weird, and of course I've got a deadline next week I'm trying to meet, and it appears that I've got everything working when I run it through VFP, but as a standalone EXE I get the (@#*@_@#(@&#$&@#*# error.