I don't want to come off as lazy. I've been working on this for quite some time now. I'm down to the very specific situation. Per the notes from Michael Washington, amongst others, I have created a single module. there are three definitions. Each definition has a default (ie blank key) control. From one definition I would like to navigate to another definition passing a parameter.

Definition: Scenarios  - Control: ScenarioList (contains a gridview in which users can select an individual scenario for updating

Definition: NewScenario - Control: New Scenario (contains a formview that inserts/update one single data row)

 Navigation desired:

  From ScenarioList to NewScenario passing key field

  From NewScenario to ScenarioList once update complete.

This is it for the moment. I hope this is the correct approach (it is the third design over 10 days). I did it this way since I wanted the gridvew to be the primary view. But I wanted to have a specific page for new creation in the main menu. Thank you for your thoughts on this matter.

Thank you for the response. I guess the question becomes determining the value of the tabID. I thought this was assigned during runtime. During my travels I started looking for a function to look up TabID by name. Hopefully, I can find that.

I regards to two controls in one definition. That did work well when navigating within the module until I wanted to place it as a standalone page (menu item). I couldn't figure out how to add a module to a page and define the key. by example a history page shows the list of reports available. On option within the list wil take the user to the edit/new scenario page. similarly, the user can select 'Submit New' from the main menu and be presented with the same control. Only difference is one is empty and one is in edit mode.

Since I will be adding about a half dozen additional controls, I thought the multiple definition method was the prefereed method. I'm open to all suggestions. Learning this is not too bad and yet can be quite frustrating.