The easiest way to use different containers on a single page is overriding the default container (set in portal settings) by specifying it in module settings (look at the advanced page settings section).

There is also an option to alter skin settings per pane, but this is a bit more tricky.

Sebastian is correct - there are mult methods of managing modules -

1 - Host/settings - defined there - and that's the dnn fallback

2 - Admin/settings - thats portal specific - and you can set both site and admin there

3 - Page specific - and for efficiency -you can setup when creating the page

4 - Module specific - which is manged in the module/settings section

5 - Skinned solution - where you can apply multi containers and they are displayed when the content appears in the site - and are hidden when no content is displayed

6 - Just to add more ingredients to the cake! - You can set the default settings of a module and how it displays throughout the site in any module / settings section and set it be the default method of module display. I use this sometimes when I have a container with all the print functions and xml functions displayed as on but want to turn them off globally - however, using that method also sets the container style for the site and sometimes I think it's just quicker to delete the action buttons in the container if I have  site where I don't want these elements displayed.

You shouldn't be bored at work today -   and if you are.. come on over to my place - I've got lots of things you could do!

Cheers

Nina Meiers