Nancy,

I would say that you should get an error when the second object in a container with the same name is instantiated. It would also be nice to get the error when you try to open the .scx at design time, or maybe when you try to save it. However, it should still open the .scx rather than making you open it as a table to track down the error.

By the way, it's the button on the .scx, not in the parent class, whose click event executes when you call thisform.cmdok.click(). At least in my test, it is.


>It's standard in OOP, I think, that if you change a parent class, children aren't all checked for conflicts like this. Same thing, if you delete a class method and you have a child with code in that method, you're S.O.L.
>
>The other way isn't great either, because that would mean that VFP would have to give us an error on opening the SCX. That might be somewhat feasible.
>