There are many shortcomings in the data features currently available in .NET. Databases don't model the objects that developers want to work with the translation between the database and the application often consumes an inordinate amount of the development effort. For example, there is no easy way in .NET to map tables like customer, address and customeraddress-x-link to an object that represents a customer which can maintain both work and home addresses and allow the developer to link a new customer to his or her spouse's existing address.

The Milos Data Components, along with the Developer Tools package, allows developers to define complex relationships between tables and to quickly and easily create and use objects that more closely represent what developers would like to code against. This approach prevents developers from using database specific code such as "SqlDataReader" in their applications. It enforces the Best Practice of separating the data access, data persistence and business logic into distinct tiers. It eliminates the need to code high level objects by hand over and over again.

With Milos Data Components a developer can specify the tables involved and their relationships to one another and minutes later be working with a strongly typed object with a high level interface such as Save() that handles the cross-links, the transactions and saving to tables in the correct order. Rules can be added quickly in a predefined place and not scattered throughout the code. The back end database can be swapped out in minutes by changing a .config file setting. Parent-child and crosslink relationships are handled automatically.