>I'm thinking along the same lines. It's the only thing that makes any sense. I'd wager that the reserved field holds the size and/or offset of the method into the methods memo field, and that, internally, VFP uses that to calculate what to display. Since internally, the memo field has the PROCEDURE/ENDPROC pair, it must use the values to determine what to display in the window in a quick and efficient method.

>It doesn't store offsets or sizes, but the order of the lines in the reserved memo MUST match the order of the PROC statements, otherwise it chokes on it.

---

Hi George,

Back in the VFP 3.0 days, I used to modify the methods field directly since it was faster than jumping in and out of individual classes and methods. I found that if I made extensive changes this would happen frequently, while if I made minor changes I rarely had a problem. I was thinking (but never tested) it was related to SET BLOCKSIZE TO , that when adding code past the (declared) blocksize that's when I had the corruption.

Since I had limited time, I decided to stay within the Class designer to avoid the whole issue, however it may warrant further investigation.