>>Is it good practice to have a form that calls another that calls another that calls another with the final one being the 'work' destination' form? Then backtracking thru them to the original. Keep in mind each one along the way has options htat can be selected.
>Timothy,
>
>RUN do not walk to yoru nearest computer book store and get "Aboput face The Essentials Of User Interface Design" by Alan Cooper publisher IDG books ISBN: 1-56884-322-4 and read it. Alan has a great analogy about this very issue. he compares it to mneeting someone in your home. He states that each window (or dialog form) that you stick your user itno is equivalent to bringing a guest into another room in your home. Each dialog has a purpose as each room in your home has a purpose. Here's where he gets his point across; he say imagine that you have a guest at the door. You meet them and they extend their hand to shake yours and you say, "No wait we have to got to the hand shaking room to do that and off you go to the handshaking room. Now you shake hands and the guest says "I have something for you here in my pocket", your reply "OK, let's go into the gift exchaning room adn you can give it to me." You do and he does and then he says "Haven't seen in a while, how are you?" You
>relpy, "Oh my, this is the gift giving room, we need to go to the small talk room to discuss that." Get the idea here<g>?
>
>Try thinkning in terms of pageframes with different configuration issue on different pages in ONE dialog that can have page hidden or shown as needed. This way the user sees two "rooms" the selction room and the do stuff room.

That gives me ideas. maybe have a main(launch) form with appropriate checkboxes
on it and proceed from there. But when the destination form opens for business should the launching form be released or hidden?