>I've just started really taking advantage of the member data stuff for a new class I'm working on. It's got a little under 80 PEM's. I tend to actually make my PEM's descriptive, so they have longer names like "nTotalAmountToGoal" or "GetPriceSchedule". I've also added them to the Favorites tab so it's easy to see them (eg. they're not mixed in with the VFP methods). I just got an error when I added a new property, "The member data for this class is over 8K in size, which is too long, so the display and favorite settings won't be saved".
>
>WTF?! Do you know how often someone is likely to run into this as soon as you really try to leverage the member data settings? I haven't even tried using this data to extend anything yet and I've already run into this.

Rick blogged here (you may have been there already)
http://west-wind.com/weblog/posts/207.aspx

Somewhere in this guy, MS claims that the 8K limit is an enhancement:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_foxhelp9/html/eca7fa6d-ec9c-411a-b3ea-6f5d71991a70.asp

From my review it seems this shortcomming is not a VFP issue - it seems to be a limition of SQL or the OS. If you were using DB2 - or IBM WebSphere - they have an update! Go figure!