Brandon --

That is very helpful information.

I had one report (in the previous version of PEM Editor) where it was unable to find a parent class, even though VFP is obviously successful in doing so. Perhaps with your help, we can track this down ... I say "we" because I certainly need your help in doing so.

What's occurring is that in reading the VCX file, in the field ClassLoc, there's a file name which VFP can find but PEM Editor cannot. That actually means that PEM Editor gets it right MOST of the time, but just not this time.

So, you say you get the error when editing your baseform class ... can you send me that class? As well as the name of the current directory, and your path statement? That would be very helpful ... at least as a first step.

Jim




>>Question, questions, I always have more questions.
>>Does it happen when it's the first thing you do after opening your VFP session?
>>Does it happen to all SCXs?
>>
>
>I've dug into this and I think I can provide some useful feedback now.
>
>If I edit my baseform class in my .VCX I get a warning messagebox from PEM Editor:
>
>**** Warning ****
>Class Library _BASE.VCX not found
>.... Continuing
>
>and PEM Editor does NOT crash VFP.
>
>If I then edit a .VCX based form who's parent is the baseform class I get the same error message but no crash.
>
>If I then edit a .VCX based form whose parent's parent is my baseform class then PEM Editor bonks VFP.
>
>
>So, from the way my classes are laid out I'll make the following assumptions:
>1. It appears there can be an issue with how PEM Editor searches for a parent class library of an object in certain scenarios (what's different about my setup is still to be determined).
>2. If PEM Editor is unable to find the parent class library of an object, then attempting to edit a grandchild of this object (one who's parent's parent is the object who's baseclass library can't be found), then PEM Editor will bonk VFP.
>
>
>Does any of that help?