John,
I ran into this confusion earily on when developing modules for DNN. The issue is understanding the structure of a page>module>control. In simple terms the page is made up of several modules. Each module has a standard display control, the view, and typically one or more admin controls (Edit, Settings, ...). You can direct DNN to open an admin control on standalone page for some aspect of your module -- it will then not display the other modules or any aspects of the orginal page - it even uses a different skin (Admin skin). For example, when you update the Page Settings for you module, you are taken to a page with just one control on it that defines the processing for the page.
So for your control, if you want the standard view to have several different "looks" then you must control this by displaying different sections (I use panels) of you view control. The Survey module does something similar -- either asks a question or shows the results, but it the same view control that does both depending on whether the user has answered the question. The Add question control is an administration control that will open on a admin page with no other moduels on the page..
If you want to display "My Report" on a page by itself, then you can create a "myreport" admin control - similar to the Edit control -- that will open by itself - no other controls on the page. Again take a look a the survey module to see how control is passed.
What if you want to navigate to a different page where there is a module that you want ... This is a bit tricky. What if the control is on several pages, which page do you jump to ??? If you "know" the module will only be one page then you can look it up using the friendlyname and determine the page (tabid) that you want to open. This not recommended but in certain instances it does work, but I would recommend reconsidering the overal module design before resorting to this....
Hope this helps.
Paul.