>Hi,
>
>I've noticed that for some reason the function message(1) in VFP 5 (I haven't tried it in VFP6) returns a bogus command line about 80% of the time. This is in an app where I have included the Debug info in the project.
>
>I can recreate the error very easily. Lets say in the beginning of the program I have the following:
>
>on error do errorhand with error(),message(),program(),lineno(),message(1)
>
>Then in the middle of the program I type this:
>
>lcBogusCommand="dsklfd;ajk;klja"
>&lcBogusCommand
>
>This will obviously return an error but instead of Message(1) returning the actual command line that caused the error, my messagebox appears with the following:
>
>Error 16:Unrecogized command verb.
>Line 42 of orphanrec
>BETWEEN(lsterm_mo,0,11)
>
>The last line is completely bogus, I think lsterm_mo is a variable in a different .prg file, not even in this project, but possibly in the same directory. Does anyone know why this happens? The actual error handler I use is below, very simple for a very simple program.


AFAIK, this happens in all compiled code. I know this is true in my error handler as well. The runtime handler does ok with LINENO(), ERROR(), MESSAGE(), but can't read the actual code that caused the error. From my experience, MESSAGE(1) gets filled with the last internally used SQL to operate on your data. This is sometimes interesting to see how VFP formaulates TABLEUPDATES and REQUERYs...