Why not just make your dataprovider & sqldataprovider class handle multiple functions for different tables?

in your dataprovider, just add defined abstract methods for the different tables.  i.e.  Then plug the functionality into your controller and sqldataprovider to match.

Imports System

Imports System.Web.Caching

Imports System.Reflection

Namespace myCompany.DNN.Modules.myCompanyUtil.Data

Public MustInherit Class DataProvider

#Region "Shared/Static Methods"

' singleton reference to the instantiated object

Private Shared objProvider As DataProvider = Nothing

' constructor

Shared Sub New()

End Sub

' dynamically create provider

Private Shared Sub CreateProvider()

objProvider = CType(Framework.Reflection.CreateObject("data", "myCompany.DNN.Modules.myCompanyUtil.Data", "myCompany.DNN.Modules.myCompanyUtil"), DataProvider)

End Sub

' return the provider

Public Shared Shadows Function Instance() As DataProvider

Return objProvider

End Function

#End Region

#Region "Abstract Methods"

'---------------------------------------------------------------------

' TODO Declare DAL methods. Should be implemented in each DAL DataProvider

' Use CodeSmith templates to generate this code

'---------------------------------------------------------------------

Public MustOverride Function ListTable1() As IDataReader

Public MustOverride Function ListTable2() As IDataReader

Public MustOverride Function ListTable3() As IDataReader

Public MustOverride Function InsertTable1() As Integer

Public MustOverride Function InsertTable2() As Integer

Public MustOverride Function InsertTable3() As Integer

Public MustOverride Function UpdateTable1() As Integer

Public MustOverride Function UpdateTable2() As Integer

Public MustOverride Function UpdateTable3() As Integer

#End Region

End Class

End Namespace

Hope that helps!

Wallew

You are correct, YourCompany.Modules.GuestBook is your class, not the table.  Ultimately, the SQLDataProvider is just executing a stored procedure.  If you write your stored proc to access multiple tables, your module will use multiple tables.

For Example:

If you have a stored proc named GetUserRoles and does something like

SELECT
  'portalname' = p.portalname,
  'portalid' = p.portalid,
  'rolename' = r.rolename
FROM userroles U
JOIN roles R ON r.roleid = u.roleid
JOIN portals P ON p.portalid = r.portalid
WHERE u.userid = @UserID

Then you have a function in your SqlDataProvider like

Public Overrides Function GetUserRoles(ByVal UserID As Integer) As IDataReader
  Return CType(SqlHelper.ExecuteReader(ConnectionString, "GetUserRoles", UserID), IDataReader)
End Function

All that's happening is the sp you call in the SqlDataProvider executes. In this example, you are accessing data from tables userroles, roles and portals to return the portal name, portalid and role name for any given user. Basically, if you can write an sql statement to do what you want in Query Analyzer, you can turn that into a stored proc and call it from your SqlDataProvider. There is no need to worry about multiple dataproviders.