>I have a form with a button named cmdOk.
>
>I want to move the button to the parent
>class, so I opened the parent class, added
>a button and named it cmdOk.
>
>When I reopened the child class, there now
>are 2 buttons with the same name.
>
>So how does VFP know which button to reference
>if I called cmdOk.Click()?
This is not supposed to happen. With normal ways of naming controls, VFP won't let you do this. (Error: object with this name already exists) Since you managed to get two controls with the same name on the same form, I suspect that VFP will manipulate whichever it finds first.
Erik Moore
Clientelligence