Naomi --

My normal advice is to install in a new folder, and re-run PEMEditor.app. Having said that, I doubt it has anything to do with your problem, but doing so would remove all doubt.

There was an earlier thread on this very issue. I believe you even contributed to it. As I recall, there was no resolution; I don't we ever did learn of possible causes of 'buffer overrun".



>>2009-08-16 - An update to PEM Editor has been released on the VFPx / Codeplex site...
>>
>>Lots of new goodies, including speed enhancements on the Document Treeview and much more.
>>
>>PEM Editor ver 4.10 - http://vfpx.codeplex.com/Wiki/View.aspx?title=PEM%20Editor
>>
>>.
>
>Jim sent me a new version of PEM Editor. I simply extracted the zip file into the same folder I already had. Should I have re-run something?
>
>Anyway, when I tried to add a new method from the Class menu I got "Buffer overrun detected". Too bad what I just changed another method of this class, which I suspect is going to be lost now.
>
>---------------------------
>Microsoft Visual C++ Runtime Library
>---------------------------
>Buffer overrun detected!
>
>Program: ...ogram Files\Microsoft Visual FoxPro 9\vfp9.exe
>
>A buffer overrun has been detected which has corrupted the program's
>internal state. The program cannot safely continue execution and must
>now be terminated.
>
>---------------------------
>OK
>---------------------------