Good it's solved Chris. (Now I'm stumped. How could a button that has focus in init could keep focus, after focus moves to another control, w/o default = .t. ). Anyway I think I misread your original posting.
Cetin
>John, thanks for taking the time to figure this out! And I certainly have no problem with the idea of the find dialog initially popping up -- it's a good one.
>
>I owe you one. :D
>
>-- Chris
>
>
>>The problem stems from the cmdFind.SetFocus() in the Form.Init. Once I
>>removed that, the Find button remained normal. However, I realize that
>>you want the default button to be Find....so...I substituted a
>>cmdFind.Click() and the Find form pops up on entry.....once you cancel
>>or OK out of that form, the data entry form operates
>>normally......so....your two options are to discard the SetFocus or
>>replace it with a click()....which is not a bad thing: Most of my data
>>entry forms fire a find dialog when you first go in.