Hi, Victor.

The others already pointed to interesting stuff. I'd also recommend you take a look at Visual Studio 2008 (due to release around the end of this year) an especially LINQ to SQL.

But I would also want to point some issues you might tke in consideration:

>The features that the product should meet are:
>3- If possible integrating Enterprise Library (application blocks).

EntLib has its own DataAccess Application Block where you should get anything like MyGeneration and build your own template. You may find something at the MyGeneration website, perhaps. Anyway, are you already using EntLib? What kind of application are you developing. While I like EntLib for some things (I used it many times) I found it is too complicated for many things. Be careful before choosing it.

>4- For the DAL (data access layer) we need that :
>a. Generates Typed Data Sets.

Sure you want to use DataSets for everything. This also depends on the type of aplication, but...

>b. Using store procedures is alternative.
>5- Easy retrieve of changes from the database schema.
>6- Easy to maintain.

>I have been testing some tools as Code Author and Dalgen. But all of them have the same problems.
> a- it is using sprocs (I would like not to use sprocs but hard coded sentences).

If you "own" the database, it could be fine to use dynamic SQL (and I prefer it, too). If you need to play with existing databases in corporate environments, you better support SPs.

> b- The BLL has to be recreated when a new field is added to the database, so if you have written your custom changes into these objects you will loose it.

This shouldn't happen if the generator produces partial classes. You should never touch the source code generated, but extnd the classes in a separate partial source. If you are using .NET 1.1 -I hope not- you should subclass from the generated class instead of modify it.

Hope this helps,