>OK, after 3 posts we get your point and those of us who worked on Codebook truly value your opinion.

It took three post to figure out how to keep "P.O.S" from converting to Point of sale. If I would have left it at that you would have missed the point and or began to question the framework. "Point of Sale" framework are you sure your problem is not there. :~)


>Have you tried redefining this class using the class browser instead of hacking it?
>
>Dan

Should not make a difference. It is a value in a memo field. Like any memo field the memo field does not care (within reason) how it got its data. I have seen this many times through the years but the problem generally goes away. This situation will not.

Which brings me to another similar problem. This app was VFP 3.0b. I opened in 7.0 and recompiled all. Fixed things that needed to be fixed and having done that I did not touch all form classes. After I deployed to production and then began to make further changes, all of a sudden I would get errors in forms that were never touched. My exe's are named like the following and sit in the production folder named the same.

SCheck.v2.10.01.exe
SCheck.v2.10.02.exe
SCheck.v2.10.03.exe
....


In .01 and .02 form A worked fine. I had never touched form A in either the old code (VFP 3.0b) or the new (VFP 7.0 SP1) and all of a sudden in .03 form A starts to have problems. I keep very good version notes and we have had to be very careful about changes (Codebook concerns PHDbase concerns ETC) so I am certain I have not done something inadvertantly.

The point is I am getting fairly confident there is memo field pointer problems for code in VCX's in VFP.

If your idea would work I would like to know how. What step am I missing ?