Jim,

Don't get me wrong I am not looking for or expecting prefect.

I work with alot of industrial software for Unix Workstations and IBM PC's used for industrial process control and monitoring.
This software is expensive ($10,000 - $20,000) and therefore of limited distribution. And most of it is filled with bugs.

We are still using a compter aided engineering program that runs on DOS. We have to carry a printer to the computer
it is on and plug it into the LPT1 port because we (and the programmer) cannot get the program to print over the network.
This program cost over $10,000 and is still sold with this bug.

As a comparsion working with programs like VFP is a joy, espacially with a resource such as the Unversal Thread to aid us.

BR Don



>Don,
>
>Obviously I'm not Barbara!
>
>There is very little information as to what VFP5.0a "fixes". There *is* a "fixlist" of sorts available from MS (possibly even in the knowledgebase *here*, but it is abbreviated and somewhat cryptic. Seems they even add to it *after* VFP 5.0a was released! Also seems that at least one bug reported as fixed was not actually fixed (something to do with printing reports and PREVIEW).
>
>But we all just accept it! Go figure!
>
>regards,
>Jim N
>
>>>>>>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