Grigore,

I can't disagree so far. I was hoping someone from the Fox team would jump in and explain how to opitmize it, but so far just silence. I suspose that silence speaks volumns.

>Hi,
>
>My suggestion would be to stop using MemberData. It plain sucks. Maybe in next version ...
>
>>I am trying Member Data in a few subclasses and forms. I love having the correct case in Intellisense, and the PEM sheet. With colors, I can deal with custom PEMS mixed in with native PEMS. But I am seeing several anomolies which suggest that the technology is somewhat immature, to say the least.
>>
>>1. Even though I have set all Member Data descriptions in the classes to Global, some of them don't seem to make it forms unless I set separate Member Data for the PEM in the form.
>>
>>2. A complex form (contains an 11 page pageframe) is taking 20-30 seconds to open for editing or to save. W/O Member Data it takes 5-6 seconds to open, less to save.
>>
>>I can deal with #1, even though it is a one time nuisance for each form, but the performance hit is just plain awful.
>>
>>Am I doing something incorrect to cause this, or is this new feature such a resource hog as to make it unusable.