Shawn,
what you ask for is how most of the core modules currently work. Take for example contacts: it's first displayed as a grid, but then users can enter data on a different control.

That second view in this case is part of the same module (Contacts) but it could also be part of a different module. All you need to be sure is that both modules use the same tables and data. In this case don't make the data dependent on ModuleID (as all core modules do) and that will be fine. Or you can tie one module to a different module using its moduleid to get its data.

Another option (different scenario) is if you want two (or more modules) act at once when any given action happens in one of them. This can be done using an artifact called ModuleCommunication. This will allow you to throw an event from a module and let other modules on the same page listen for that event.

---

Vicenç Masanas
Banyoles, Girona - Spain