>Hi Tamar
>
>>MemberData has a really strange inheritance scheme. For each attribute, the following happens:
>>...
>
>Thanks for your detailed explanation
>
>
>>4) the global MemberData store (in the FoxUser table) is searched. If there's a value for the attribute there, it's used and the search stops.
>
>Does this mean (in my context at least) that I can create _MemberData of all the c-Level methods / properties at the i-Layer and make them Global so they automatically appear so at the c as well as i-Levels?

If you make MemberData global, it applies to any object that doesn't have its own MemberData according to rules 1-3. However, it lives in the FoxCode (I said FoxUser before and that's wrong) table, so applies only on that machine.

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.

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.

Tamar