I only came accross this because I was moving
the button up a level so I could get it on other
subclasses and I went back into the child to remove
it and noticed the name was the same on both.

If you think about it, theres no way to prevent this.
FoxPro can't possibly track down all your subclasses
and rename buttons. Not only would that be a nightmare
to do, but it could break alot of code.

Personnaly, in forms, I never put code in buttons anyway.
I usually place a call to a form or parent method
in the click event of the button, that way if I want
to change to a different control, I dont have to cut
and paste alot of code, unless its a composite class.

So even if I did leave the two buttons on the form, it
would still work; its just a weird phenominon.