Hi, Pascal-
I read your answer, and it was correct--well, at least I should say we seem to agree ;). You just didn't freak out like I did! < bg >

Seriously, I think it's "buggish" but when I got to thinking about how in the heck FP was supposed to correct for something like this, I couldn't come up with a way.

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.

>Sorry Folks,
>
>I guess I did not read the post properly.
>
>This is really weird behavior...
>
>;)
>
>Pascal