I understand the problem very well. PEM Editor crashes VFP in that class.

Can't you just close it and not use it when you need to work on that class? ... and then re-open it later?

>>Well, I can certainly imagine the steps to do so.
>>
>>There will be some help for this in release 5 -- PEM Editor will provide a menu option so that the next time that it is opened from the VFP system menu, the default VFP "Edit Property /Method" will appear, rather than PEM Editor.
>>
>Thanks
>
>>Hmmm -- am curious. Do you need the default VFP "Edit Property /Method" dialog very often? In my own experience (before PEM Editor), I found that it was not a tool I used very often.
>>
>Me too.
>
>>If that's so for you as well, then I would suggest installing PEMEditor without having it replace the "New Property" and "New Method" dialogs; close it when you are going to work on the class which always bombs; and only do the uninstall / reinstall when you need the default VFP dialog.
>>
>I don't know how Noami described the incompatibility between the 2 to you, but in my case, with that class opened, I don't need to "Add new" property or method, as soon as I switch to main view of PemEditor, I am Buffer Overrun! So to me the only solution if I need to work on that class is to do away with PemEditor totally...