>>>>>I'm going have to say, that's poor design. There are still mouse-challenged users and some that physically can't use a mouse.
>>>>>
>>>>>>Seems like there was a MDOWN() command that I could put in a (VFP7) command button to only allow Mouse access (not keybd). Maybe I just don't know how to use it?? Maybe there is a better way?
>>>>>>Thanks,
>>>>>>Randy
>>>>
>>>>We don't know anything about his interface. Maybe He wanted left keyboard just typing and don't want let call button with invalid keyboard strikes or something else...
>>>>
>>>
>>>Exactly! When we don't know enough about the UI why is it that the first reply is always, "Don't. Its not standard practice. Microsoft guidelines says blah, blah, blah." If it was an absolute no no to not have this functionality (along with flashing text - another one that brings out the same response) then why does the tool (VFP, etc.) allow for programmers to do so?
>>>
>>>
>>>>I wondered why if it's easy to tell us?
>>
>>A car allows drivers to do 1 mile an hour on the highway and 120 miles an hour in a school zone. Just because the tool allows something does not make it smart for the programmer to use the features any way they feel like.
>
>Sorry, but, your analogy doesn't work here. We're talking about a computer program user interface and not the risk of endangering one's life (or others) in a car!
>
>See my other post in this thread about having the ability to say "I don't give a rat's a$$ about standards".

A screwdriver can be used to ________, if you don't care about standards. I agree programmers want the freedom to do anything, but more often than not, they do not need it. I've seen some really dumb stuff and the programmers patted themselves on their proverbial backs for their perceived ingenuity.