>>>>>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, plesase 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 seem to be cutting down the amount of code which is garbled.
>
>I am down to only the click method of two cmdButtons garbled.
>Before all the class code was. Unfortunately I compiled the
>classlib, ran the object checking only the click code for one of
>the buttons. Then I deleted the User File and noticed the other
>code was cleaned up. What I am saying is I do not know which
>action cleared the code that was cleared.
>
>But nothing helps the code for the two buttons.
>
>I will delete them and re-enter them to see what happens.
>Thankfully I have a current printout.
>
>Thanks for the help
>
>Don


I am answering myself.

Re-entering the code did not work.

The code I thought was not garbled was ANSI code from a different snippet.

(Normally the grabled code is beyond displayable ANSI characters)

I worked over the weekend on this.

The only time I have this problem is when I debug a class library - especially a form.

I do not have the problem with .prg files or for that matter with class code based on custom classes. It seems only to be a problem with visual classes.

I have switched to working on my forms in code instead of visually. This is not a problem for now since I am working on "standard" forms, ArrayPick forms, message boxes etc. which I usually change to code eventually anyway.

It will be a serious problem when I go back to working on Application specific forms which I like to keep "visual".

It seems to be a problem with the debugger. I work on a Win95 station at work and a Win NT 4.0 (in a portable) at home. (We are converting to Win NT at work too. - the portable is new).

I have the same problem at both places.

The debugger has crashed under NT while having this problem.

However it only does 1 out of 10 times. I cannot force it.

Sometime compiling the class library seems to solve the problem. Sometimes switching the debugger from Debug frame to Fox frame or back solves the problem.

But neither are sucessful all the time.

I am working with version5.0 dated 21 August 1996. I am getting version 5.0a to see if this clears it up.

Best Regards Don