After studying the tutorials and docs on module design, and looking at a few of the free modules, I was wondering if I have this correct:
1) Taking the control (UI) and data tables into consideration, I create the objectInfo class, which has regions for each data table and "view" (or stored procedure that returns results of joined tables from queries)
2) Then I take the info class and build forward to the controller, etc.
Is this correct? I can't find too many samples using the newer item template (4.02), but after reviewing the BLOG and STORE modules, they seem to have everything wrapped up into one xxxxInfo.vb class file. Almost all examples are for a one table simple scenario.
Do I need to create a region for the Info of any table that will never be directly called or edited (only used to tie normalized tables together)?
Thanks in advance