That's a common technique which I prefer (particularly for multiple view controls).  Here are several pointers for its use: 1) Create a base class (itself inheriting from PortalModuleBase) for the dispatch or master user control as well as the child controls. This base class will contain all of the common properties and methods needed by the master and child controls and makes type casting of the object returned by LoadControl easier. 2)  After the child control is loaded, pass the ModuleConfiguration from the master control to the child control to provide easy access to ModuleID and other properties of your module. 3) If you are using localication, I seem to recall that you will also need to pass the LocalResourceFile property from the master to child control.

Another (and more straightforward) way to accomplish this is to use DNN's own pattern of defining each module control with a different ControlKey then using one of the overloaded methods of NavigateUrl and/or EditUrl to to redirect to the proper editing control based on a link, button, etc. in the master control.

Yet another approach is to have all the editing done in one module control with the appropriate sections hidden or revealed using panels, divs/table rows, MultiView or Wizzard controls.  Unless each section is relatively short, I find this leads to some large and hard to follow .ascx files and multiple code branches.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner