DAAB V 2.0 and Updates

This version adds code for Updates like this:

Public Overloads Shared Sub UpdateDataset(ByVal insertCommand As SqlCommand,
ByVal deleteCommand As SqlCommand, ByVal updateCommand As SqlCommand, ByVal
dataSet As DataSet, ByVal tableName As String)

I am shocked to see Command objects being passed to a DAL.  I used DAAB V
1.0 months ago and extended it for updates, adding the exact same method
name, however the only thing passed in is a connection string and a DataSet.

Our DAL will be for us, and us only.  It will always hit SQL Server.  It is
'OK' to send SqlCommands in this case?  If yes, then this sure makes my job
a lot easier as far as coding for Inserts 'generically' in our DAL.