Previous experiences have extensively demonstrated how often an application’s requirements are directly derived from the database model. Many of an application’s forms used to manage data in the database require only simple validation to assure the integrity of the data before passing it along to the database. In order to leverage this realization, the Design Studio component uses the database schema of any SQL Server or Access database to automatically generate a web based interface to maintain the simple data structures of the database. Stored procedures and data access code are created to facilitate the data querying and updating processes. Business objects for each database table act as cursors to navigate the data retrieved from the data access calls. User interface forms provide data editing and validation for each business object.

Documentation  DesignedNet Framework Requirements, architecture and design Object Model Reference Library object model description

    Database meta-data schema is used to automate stored procedures and data access code implementation for all common record operations: Insert, List, ListByForeignKey, Exists, Select, Update and Delete. Business entity objects are generated to wrap each data access function and provide cursor based access to data via named and typed properties. Entity object model interface directly mirrors database schema including field types, length, null-ability and foreign key relationships. User interface web controls allows for immediate management of entity data lists with field type and requirement form validation derived from table schema. Base class library provides minimized application memory footprint while maintaining comprehensive functionality. Interface library allows for custom class implementations to leverage common DesignedNet Entity Framework operations for reduced code-management requirements and easy portability between SQL Server and Access data stores.