This is no news - remember the FoxPlus editor, which placed chr(141) instead of cr, and invariably placed EOF at the end of file? Once you opened such one in FP1.0x, you had all the trouble to convert. And if you oversaw the EOF marker and started typing beyound it, these lines were never compiled or run.

I think this could be simply solved by treating "text beyond EOF" as a compile time error. I know the editor doesn't put EOF marker by default, but it may come from many other sources (generating scripts or pieces thereof using Set Alternate comes to mind).

>We had a somewhat similar support case where it turned out the MPR file contained a chr(26), which is an end of file marker, in the middle of the file. Any procs after that character could not be found. It took us a while to pin this one down.
>
>>Hi Vim,
>>
>>First check the mpr file to make sure that procedure _2b231j80 is in the file, IF it is, step through invoking the menu bar that calls procedure _2b231j80 and figure out why it isn't in scope.
>>
>>pamela
>>
>>>i have a VFP 8.0 app that works fine on my PC at home. i copied the source code to my friend's pc and he is getting tons of errors like this "procedure _2b231j80 not found" when he clicks on menu choices. we copied over new version of the menu files - mnx, mpr, etc - and it worked fine for a bit but now the errors have start again. any suggestions?