I don't think that the PM use of the DD would work well in .NET. It's doing the work inside of it's own .APP, correct? It creates the code necessary to access the data & more. In .NET your no longer tightly coupled to your data. Your going through a data layer via a data set or a data pump.

__Stephen


>While we are at it -- how about an active data dictionary? I have used the Promatrix framework for VFP extensively over the last couple of years, and gotten so used to the data dictionary that working without one seems like living without electricity and plumbing. This particular framework has an add-on product that will import database schema designs directly from xCase (a database design CASE tool for VFP, SQL Server, Oracle, MySQL, InterBase, etc. backends) into the datadictionary, and boy HOWDY does that one make my life easy!
>
>Data dictionary can maintain and insert a whole bunch of properties and methods/triggers for each data item, so that setting up controls is very easy (drag from data dictionary, drop onto the form). Same goes for various utility functions and data integrity management.