What if you put in (temporarily) a NODEFAULT for the code higher up the class hierarchy?


>Mike.
>
>No doubt it'll turn out to be silly, but it's not spelling. As I mentioned I added another property with an access method that doesn't fire, and none of the access methods in the class seem to be firing now.
>
>Thanks though. If you have any more ideas, toss me a fish. :)