Sort of. You could do it with one module containing two different controls.

BUT - in practise it's much the same as two different modules. It's the developer's problem to manage communication between them. In principle it's easy - have them share the same DB table rows. Ooh ooh ooh but wait. What if I want to use the module again on another page? Will the two pages interfere with each other? Yes. Unless the developer writes the code carefully enough to make it work the way s/he wants.

---

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk

you can also use the built in "copy module" functionality - http://www.dnnsoftware.com/help#Docum... module . I've used this before in modules where I stored layout options as a tabmodulesetting e.g. I had a module where I had a setting for "list" and one for "detailed", I added a module to a page and added a bunch of data to it (a list of links with related content), and then copied the module to the same page but set it to "list" so I ended up with a list of links in the left that when I clicked show content in the middle pane.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US