Hi folks,

I believe I may have slammed up against a (potentially annoying) limitation of the new MemberData functionality of VFP 9.

When the Settings/Scope for a property or method is selected to be Global in the MemberData editor, the length of the property is limited to the width of the Abbrev field in the FOXCODE table. This field is currently sized to 24 characters wide.

As it happens, I just created a method called PopulateContainedControls as part of a container class. That method name is 25 characters long. The MemberData editor accepted the value and showed the correct capitalization. However, when I subsequently edit that class (or any subclasses of that class), the method name does not show ANY of the MemberData changes (basically, it's incorrectly capitalized and shows up at the bottom of the Properties sheet).

This had me banging my forehead on the monitor for a few moments, until I decided to check the entry in the FOXCODE table. The Abbrev field for the entry read POPULATECONTAINEDCONTROL -- cutting off the 'S' at the end due to its length.

This brings the following questions to mind:
- Is this limitation documented ANYWHERE? (and yes, I know that the FOXCODE table and its structure is well documented in the help file)
- Can I just increase the size of the Abbrev field in my FOXCODE table? What other tools that use that table would break if I did that?
- Has anybody else run across this, and what actions did you/they take?
- And, more importantly -- a 24 character MAXIMUM??? I can't believe nobody caught this (including myself -- and I used the heck out of this in the public beta).

As most of you know, I'm not one to start screaming "BUG!! BUG!!" every time I find something that doesn't appear to work the way I personally expect -- but this one DOES seem to be a limitation that should probably be addressed.

UPDATE: The second question above is answered. You *can not* change the structure of the FOXCODE table. When you attempt to assign that table to the _FOXCODE system variable, you get an error message that the table is corrupted or incompatible. So, that idea's out.

All other ideas and/or constructive comments are solicited and appreciated...

TIA,