Hi Jim,

good question.
It might be that the Document view was open, but I'm not sure. It was some time ago. I can not reproduce, the _memberdata is all killed.

Agnes
>Agnes --
>
>Am curious about this -- when I've experienced problems like this, it was because I had the Document View window open. When I closed that, loading a dense form was a lot better (but not great). Is it the combination of the two?
>
>Jim
>
>>Hi Doug,
>>
>>yes, I see. Simple I never use _MemberData because it's a pain if used multiple if I have a lot of props and a lot of objects with thise props. If tried this once with a container with 300 objects. I needs minutes to load. Global store is much faster. So for me is the missing global store a stop.
>>
>>Agnes
>>>Hi Agnes.
>>>
>>>>-alters _memberdata. May be set off. No option for global store. I need option Off / _MemberData / Global as optiongroup (on my fingertips)
>>>
>>>Actually, this one is easy. If you enter a member's name in mixed case (such as nTest), PEM Editor will either create member data for it or not, depending on how you have the "Do not use or create _MemberData" option set. If you enter the name in all lower case, regardless of that option, PEM Editor doesn't create member data. So, you can complete control over what members have member data. It doesn't currently handle global member data, but that may be added in the future.
>>>
>>>Doug