>>>>Help. My sessions in the debugger show garbled code lines.
>>>>
>>>>I assume it is showing an intermediate or machine code for Foxprow since the code runs correctly as I step thru it. I just cannot read the lines of code.
>>>>
>>>>All I can read is any literal text, enclosed by quotes.
>>>>
>>>>The code in question is class code from a .vcx file.
>>>>
>>>>*.prg code reads fine.
>>>>
>>>>Please help!
>>>
>>>Don, try doing COMPILE CLASSLIB Mylib to see if that will 'update' the code.
>>>
>>>HTH
>>>Barbara
>>
>>Tried it but it did not work. Thanks for trying.
>>
>>Still, please help!!
>
>Try exiting VFP, deleting your FoxUser.DBF and re-starting VFP. I've had problems with random junk appearing that this cured. Sort of way out.....
>
>Barbara

I have worked for a number of days with this problem.

It seems to be associated with use of the "Fix" option of the Debug frame.

If I avoid using it I seem to have no (or fewer) problems.

I have many more of these problems when I use the "Fix" option.

However I cannot not reliably reproduce the problem by using it.

Just as I think I have avoided the problem it comes back. I actually changed a method in a form by adding 10 to 12 lines of code, I ran it in the debugger and
used "Fix" option of the Debug frame menu to switch to editing. The next time
I ran the debugger it showed me the 'old' version of the method while stepping through the code. And it was somehow running the old code.

If I then picked "Fix" it switched me to the new version of the method. This can drive you nuts.

Naturally I can live without the using the "Fix" option. And I can live with the occasional Debugger program crash. But this makes me worry what else is hiding in this program.

Sorry, on to my question. I have purchased version 5.0a from Microsoft. However it will take 3-4 weeks on back order to get it here. Is there a reasonable chance this upgrade will correct this? There is little information on what this version corrects.

Thank You

Don