Naomi --

Thanks for the clarification. That's why I said "apparently" -- in the only case that I have been supplied where this error occurred, I was able to reproduce the error in SP1 but not SP2. It was my hope that this meant it was a corrected problem in SP2, but I see that's not the case.



>>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.
>
>The last statement is not correct, since I got that error with SP2.
>
>BTW, is there a way to assign New Property/Method menu to PEM after I already installed it and chose No initially?