At its core, DNN is a PAGE based framework
 - each and every call to DNN revolve around a request to the default.aspx web page.

And what is displayed is controlled firstly by the SKIN associated with the site, then by the TABID passed to default.aspx - and finally by the Modules that are associated with that tabid - and arranged according to their placement on the SKIN.

SO as such - you extend the content of a DNN site by writing MODULES.

Having said that - what Im wondering - is what exactly you are trying to do - and what is the point of these Multi-Page apps you are referring to.

Westa

You see - the reason for using Modules - is because thats how you extend DNN   -  not because of some Idea of posting things back

Postback is not something that is a DNN thing - but instead Postback is all todo with how Asp.net works - and where it gets its power from.

Westa

Terry - what you describe is one module

Basically a module can have one or more 'pages' (really ascx user controls) that is uses

Your first is the view control - this would list all the events

clicnk on an event and this would load the kind of ticket control -

you load these differnt views by using the EditURL or NavigateURL function to pass parameters to the module in the query string

Each control has an id like the view one (or default) is a blank or null id and the edit one is usually 'edit' but you can hanve more if you need as long as you keep the chain or display views clear for yourslef

you might take a look at the code for the text/html or links  moduel and how it is registered as a module in the module definitions for a good example  

Terry - if you want I can talk you through it on IM as well (dylan.barber@earthlink.net on MSN IM)