Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Standalone EXE vs. Do'ing EXE in Command Window
Message
General information
Forum:
Visual FoxPro
Category:
Coding, syntax & commands
Title:
Standalone EXE vs. Do'ing EXE in Command Window
Miscellaneous
Thread ID:
00209495
Message ID:
00209495
Views:
54
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.

Thanks in Advance.

Kevin
Kevin R. Hunt
Next
Reply
Map
View

Click here to load this message in the networking platform