>
>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().

Thanks for your answer James.
In mi case is returning that the line of code is sp_MyStoredProcedure(),
where sp_MyStoredProcedure is a trigger in a table that stores a log
of the errors, but I know the error is not there, how are you suppose to
track this ?