Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why does MESSAGE(1) reports different at run time ?
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00460083
Message ID:
00460085
Views:
13
>Hello everybody,
> I am working in an error trapping routine and I have the next problem,
> MESSAGE(1) shows one thing under development and other thing at run time
> When I run under development myApplication.exe, which calls MyErrorApplication.app MESSAGE(1) shows the line of code
>with the error, but , when I run myApplication.exe outside FoxPro it
>shows me something totally different.
> Why is that ?
>
> Thanks much in advance.

From the Hacker's Guide:

MESSAGE(1) is a funny function. When you're running the interactive version of VFP, sometimes it returns the original line of code even if the program file is specifically compiled with the encrypt option! Sometimes, rather than displaying the entire line of code, the error handler translates the tokenized FoxPro command into its original form, and displays it with an ellipsis if additional information was included in the command. The Help claims this occurs when "the source code is unavailable." We've usually found that to mean when the source file is not in the current directory or on the path. Finally, in the runtime version, MESSAGE(1) returns the same error message that's displayed with MESSAGE().
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform