Hi

>My take is that you should use global MemberData for things that apply across a wide number of class hierarchies (PEMs that belong to lots of kinds of classes). For everything else, do it at the top of the class hierarchy, that is, as soon as the PEM is added.

Yes, I like the idea. Thanks a lot.

>For what I consider the most important aspect of MemberData, getting the case right, you can save a lot of time and effort by using the better Add Property/Method dialog that Doug Hennig wrote. There's a version of it in the Solution Samples, but there's a later, better version at VFPX.

Yes, I have already done this so for the newer PEMs I have a lot of effort saved.

Thanks.