>>> It's been my experience that money talks... and if the client wants it and will pay for it, DO IT. I'll make mine stand on its head if that is what the customer wants.
>>>
>>> Remember, the customer is always right. <g>
>>>
>>>
>>>Wayne
>>
>>
>>I strongly disagree here. As I said in another posting on this thread, "The customer is always right" is not always right. The job of a consultant is to consult, just like an attorney or accountant or doctor. If the client is worng it is our job to tell him...it needs to be done carefully...but we should tell him.
>
> You are saying that you would lose a contract if a client wanted something that did not adhere to the Windows standard? We are talking about a very simple change that may make the workers at this site more productive. From a business stand point, what you are saying makes no sense.
>
> Just because someone somewhere puts something down in print and says that you should follow it does not mean that you have to. If it makes sense to deviate from the standards to improve the overall functionality of an application, or make it more user friendly, you should.
>
>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