s2k, EntitySpaces is a better DAL, and you can point, click, and generate it for you entire database in seconds, and now we have full hierarchical support. EntitySpaces is extremely simple to use compared to the DNN DAL, look at the sample guestbook module on our site, you can see the source, it's very intuitive and simple to use, supports transactions, serialization, LINQ, design time data binding, and best of all, it provider independent without recompiling. Our NUnit Test Suite is a monster, and we run the same exact binaries against SQL, Oracle, MySQL and Access.

The whole point of EntitySpaces is that it is not complex

Mike Griffin
EntitySpaces LLC
http://www.entityspaces.net

Flexibility is just one of the advantages EntitySpaces brings to the table. All our generated code is in an abstract class. We then provide you with an empty concrete class to implement whatever custom logic you would want to apply beyond what we already offer. Consider this example from an Employees table.

  public bool CustomLoad()
{
       Select(EmployeeID, FirstName, LastName, TitleOfCourtesy)
       .Where
       (
              Or(LastName.Like("%A%"), LastName.Like("%O%")),
              this.BirthDate.Between("1/1/1940", "1/1/2006")
       )
       .OrderBy(LastName.Descending, FirstName.Ascending);
       return this.Load();
}



Then in your application you can use it like so

EmployeesCollection colEmployees = new EmployeesCollection();

if (colEmployees.CustomLoad())
{
     //Do whatever
}


EntitySpaces generates the CRUD\Dynamic Query code you will need, and allows you to add any custom methods you may require. Additionally, when your db schema changes you can regenerate and the abstract classes will be overwritten, but your custom code will remain intact. Just trying to illustrate the flexibility of EntitySpaces and how it solves the very issues that concern you as they are common, not sway your opinion s2k;)

Yes our scripts do put in the {objectQualifier}{databaseOwner}.