>>IMO, what you're asking is not good OOP design. 

IMHO, VFP is not allowing me to design a good OOP

It acts (Randomly Science) when it comes to OOP

DISP MEMO  <-- Gives you 84 Public System Variable, some that can be used and changed and they are visible to all class method.

I know that 1 public variable can break the encapsulation.

I want to see the PEMs in Proper Capitalization, No, you cannot, you should convert your class to DLL to see it, Each dll will add 2 entry registry (AFAIK)

I want is to show object inside object in dll in order to see it in the intellisense, No, I should use a a complex code as Sergey posted Calvin Code

I had try every possible code I found on the internet in order to see an object inside dll and fails. The only way I found is to add my dll as object to _screen
in _screen I can see the object and it is PEMs available in the intellisense. but NOT in  my dll.

Let me ask you 2 question.
1-  If I change the session to custom, AddProperty() will available by default if I did not use Hidden keyword. Is that bad OOP design?
2-  I know that you SHOULD expose as many method as you want, but the good OOP is measured by controlling the Property value (Set/Get) ?

--> The internal workings of the class should be hidden from the outside. By allowing the outside class to AddProperty on another class, you're exposing the inner workings.

I am asking for my above question just to try to see If i can use AddProperty() to add object to my existing dll property. With Sergey response I can do it.
So I guess I will no longer need in my current framework (so far)

Thank you for your advice.

Sorry to post my answer as code, but it refuse to be posted unless i add PRE /PRE