Larry,

>I'll use your message to respond because you were the first to counter my opinion *s*.

I didn't mean to start a vast controversy. *g*

>What I am thinking about is the ability to change the background color of a command button in my application. When I as the almighty developer have deemed it prudent to change the characteristics of one lone button in my application, I shouldn't be forced to MacGiver something together using bubble gum and paper clips.

If the user switches from Teal to Pumpkin to Eggplant to some custom color combination our apps should adjust. We cried out during each of the FPW years to allow our app to look exactly like every other windows app in this regard. I'm happy we finally do fit in.

>As Nick mentioned in his post, we are inundated with color meanings all the time. Stop lights are REDGREEN. These coliors mean something.

Be warned, not all colors mean the same thing to ALL cultures. I don't have a concrete example at hand this moment but it is something I've read somewhere.

And another point Nick brought up that I want to expand on. Forms, labels, shapes, text, etc. all have properties to set the backcolor. If we are to assume that we are never to touch the color settings because the user should always have control in this arean, then why do these items have this property? Why is the development handicapped in this way? Did the team in charge of command buttons say, 'Oh no! We can't give developers the ability to change command button colors'. And at the same time, all the other members of the VFP developement team thought, 'What the hell'.

The bottom line is the User is in control and that's more important than Us programmers being in control.

>One last thing. For those who said that the end user's color selections should be sacrosanct, is there any color in your applicatios at all?

Yes, my apps all user the user's desktop color choices.