Data Persistance Layer

Hi,

I'm looking for a good solution that generates entity classes and database model (access and sql) and some classes to enable data access (preferably 2005).

So:
- you design a class diagram and the database and classes are auto-generated + data access logic
or
- you create the database and the classes and are auto-generated + data access logic
or
- you create the classes and the database is auto-generated + data access logic

I can live with any specific naming conventions as long as they're consistent. For data access I would need these:
- load one object by ID
- load all object for one entity type
- load filtered (with a where clause expression)
- load sorted ?
- load filtered and sorted
- save/persist (insert or update) one object
- delete one object

Ofcourse there would always be additional work on indexes/views, so not everything has to be perfectly made. Just a good framewor ...