>>>Wayne
>>
>>I agree with you, Wayne. A perfect example is a set of menus that encourage a user to perform certain tasks in a given order -- for good business reasons. Having the menu drop back down and re-display the last choice helps the user remember what step he/she performed last. Craig: You may like having to use the mouse to re-pull down menu/submenu/subsubmenu/subsubsubmenu for one item, then do it again for the next one, but I find it a royal PITA -- like for re-setting object font and size and style -- which can't be done all in one step. That to me is just a stupid waste of time. The religious-windows crowd and I will ALWAYS disagree on that.
>>
>>Rob
>
>No, I'm not saying that. As I said, if the intent of the original poster is to Add records, I'd just leave the form in Add mode after the data is saved. If it is necessary for the user to perform steps in a certain order, then I would use a wizard or page frames. BTW...I'm not in the religious-windows crowd. There are many things in the Guidelines that I don't follow....but things like menu control I think are important. I don't want my applications to behave differently than other Windows apps because it actually increases training time and annoys the heck out of the users. As for the example of selecting the menu several times to set font properties, I agree with you.

Hi Craig:

Glad to hear you don't always follow the guidelines. I think as developers, we need to keep them in mind, but always do what's right for the client, or what he demands. After all, the client pays the bills... It just didn't sound like you were willing to go so far on that... Anyhow, disagreements can sometimes enlighten both sides, if they are open-minded...

Thanx for the feedback.

Rob