Absolutely! that is much better than not being able to use PEMEditor at all, or crashing every time i access those classes...only 1 in my case. Then once i encounter the problem, i can set the switch, and still access the class via PEMEditor.

Sounds like a good workaround to me.

Thanks, J
>Howdy all --
>
>I have given this problem additional thought, trying to find a workaround that will help those who keep getting blown away by these frustrating 'Buffer Overrun" problems.
>
>I do not think we can find a way to correct the actual problem, merely a way to avoid getting blown out of VFP.
>
>So, I have a proposal for those who are having this problem. It involves providing the capability to temporarily disable a small part of PEM Editor while working on these problem classes, as follows:
>
>
>There would be a new option in Preferences, a checkbox which would be used only for those classes experiencing 'Buffer Overruns'.
>
>When this checkbox is checked on, PEM Editor will skip the statement causing the Buffer Overruns will be skipped.
>
>The effect of this will be that PEM Editor will not display the descriptions for PEMs -- in fact, in will not even allow you to enter descriptions.
>
>
>The idea here is to temporarily cripple PEM Editor (just a bit), so that most of its functionality is still available. Thus, you'd want to turn this switch off again when working on all other classes.
>
>There is one drawback -- you will have to know which classes will cause this problem and change this flag BEFORE opening the class -- as you know, PEM Editor will croak as soon as you open the class.
>
>Any thoughts on whether this would be a satisfactory workaround for this problem?
>
>Jim
>
>
>
>
>>There have been a few reports over time with "Buffer Overrun" problems in PEM Editor. These errors crash VFP.
>>
>>This message is a status report on what I have learned about these errors.
>>
>>The actual error is an error in VFP9 SP1 and is completely independent of PEM Editor. The error can be reproduced when PEM Editor is not even open, by doing the following:
>>
>>(A) Open up the form or class where the error occurs and, if necessary, select the appropriate object.
>>
>>(B) Execute the following three lines, which should create an array called aMemberList containing, among other things, the descriptions for all the members:

? 0 # ASelObj (aObjects) or  0 # ASelObj (aObjects, 1)
>>aObj = aObjects(1)
>>? AMembers( aMemberList, aObj,3)

>>The last statement is the statement, as you will see, where the Buffer Overrun occurs, bombing VFP.
>>
>>Unfortunately, there appears to be no way around this:
>>
>>(1) Obtaining the list of member descriptions is an integral part of PEM Editor and cannot be removed
>>(2) There is no known alternative to aMembers to obtain the list of member descriptions.
>>(3) The conditions which cause the error are not known, so it is not possible to simply bypass this code conditionally.
>>(4) It is not possible to capture the error when it occurs; VFP just crashes.
>>
>>Note that this error occurs in SP1 but apparently not SP2.