Hi here,

im still searching for answers of my questions for Module Development with Multiple Tables. All what i can find around the whole world are explanations oubout Module Development with one table. But what is when you need create a more complex Module. 

I have still 31 tables with a lot of Relations and from this i need create a Module. Anybody here can tell me how i can realize it???

Thanks for answers or hyperlinks where i can still  solutions,
James

Hi Michael,

thanks a lot for the fast and detailed answer. This have help me a lot.
James

I think it is based on your approach when developing an application.

A module is just an asp .net application-like based on DNN terminology. Using database or not is based on your business scenario. I what you accomplish is just to simplified your development when working with a lot of tables, for example to reduce about writing a lot of custom class, then you can use an ORM tools. If you have time, then you write your own custom class one by one or, as an alternative, you can using code generator. There are a lot of ORM tools like :

• nHibernate (http://www.nhibernate.org )
• SubSonic (www.subsonicproject.com)
• LINQ (http://msdn2.microsoft.com/en-us/netframework/aa904594.aspx)
• ADO .NET Entity Framework (http://msdn2.microsoft.com/en-us/library/aa697427(VS.80).aspx)
• others

Those are comes with different advantages and disadvantages. But the main goal is the same, to easier your development time. For example, by using SubSonic you will be helped to generate custom class based on your table on the fly. So does the stored procedure. SubSonic will generate all for you. By using LINQ, you can simplified your query using sql-like syntax but in expression level. You can choose whatever ORM tool you like.

CMIIW.