The reason for the DNN DAL is to act as a data abstraction layer.  That potentially allows modules to access
different data providers - MYSQL, ORACLE etc

But in reality - for most module developers - they have not real need for this sort of functionality.

As a result - unless you really need that sort of level of abstraction - you dont actually need to use the DAL at all
 - you can just do calls to SQL the same as any web application.

The DAL+ module outlined by Michael Washington elsewhere on this site basically follows this approach.
It still offers a object based access methodology but without the need for the complexitie of the full DAL model.

Going further beyond this - if your modules are for your own use - and you dont plan for public distribution
then you can even bypass this step - and just use calls to SQL yourself and handle the access the same 
as you would for any web application.

In reality - think of the DAL and DAL+ models as guidelines - even the DNN core developers have this attitude.
Since in recent months the advent of .net 3.5 and LINQtoSQL has thrown yet another option into the mix - which is
currently being recommended by Michael as the way to go for future DNN developments.

Westa

PS - LINQtoSQL is looking really great - but it does have a major deal breaker for DNN access - currently there is 
no easy way to implement the DNN prefix concept at the LINQtoSQL level