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

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

In my next ASP.NET app I have to do a multi language for a plant located in Mexico. Going to be fun. A select statement for labels and another for Data Entry. The joy is going to come from a UI for new languages, so we can get a bi-lingual from any new language and have them add the new labels as needed.

__Stephen


>Hi,
>
>I agree with Pertti that an Active Data Dictionary is hard to live without once you have used one. I have also been using the VPME framework and have recently been testing .NET in conjunction with a VPME application's data dictionary in SQL Server and the combination works well - both with web and win forms.
>
>Personally, I am a strong believer in data driven applications and an Active Data Dictionary is key. Whichever way you look at it you have to store your basic configuration data somewhere - even if it is only the field captions before multi-lingual translation. Why not expand on that and have a powerful dictionary sitting in the middle of your .NET applications ?
>
>Regards,
>
>Aaron