Guys, I'm looking at creating a VB.NET application to replace an existing Web-based app which is used to create/edit/delete Active Directory users, as I'm starting to hit the usual limits associated with Web-based applications. My question is this: what is the best method for creating the individual windows for each of the functions? The create user function (for example) goes through the following screens (ie, a new web page pops up for each step): Collect user details Confirm that the account isn't duplicate, suggest alternatives if it is Present AD tree and determine from the user which container the account will be created in If a template user was supplied, get the group membership from the template user and apply the same to the new one Confirm all details are correct with the operator before doing all the work Traditionally with VB6, I would have done this as an MDI application, with each of the ''functions" being an MDI child. Something like the new user function for example would probably be better off being a wizard, but my big concern is that the user might get lost having more than one MDI child open at any one time. What is the best way I can achieve this using VB.NET?