Hi,

>>I see the need for Meta Data, the same thing that VPM, VFE, MM, ... all have the ability to use in VFP.

Whether it is called Meta Data or a Data Dictionary I really couldn't care - so long as there is one and it is powerful enough to drive commercial applications by giving them as much flexibility as possible.

>>Now lets get to the heart of this. You don't have a Data Engine as part of your GUI. Period.

I never said the data engine was part of the UI and I don't know how we got to that one<g>. I think Pertti simply made the point that it would be good if MM.NET had support for an Active Data Dictionary. If it is good enough for VFE, VPM and even MM.VFP to support data dictionaries and data driven multi-lingual translation systems, then I think it is a fair point to raise for MM.NET.

I don't know where the confusion has crept in but I believe that we all believe in storing "meta data" in data. Anything else is hardcoded hell.

Regards,

Aaron