>Not sure I understand the question. I think the answer is that the validation code is in the subclass, not in the instance on the form. That, after all was the point of subclassing it originally. I have three separate forms which each require the same date field with the same validations, so I figured it would save repetition if I did it once, got it working, then subclassed it and used the class in all three forms.
>
>I'm sure its something to do with hierarchy but haven't a clue what implications that has or what to do about it. All I do know, as I said to Craig, is that the original version (prior to subclassing) works exactly as intended.
>
>> Do you have something like:
>>
>>return llCondition and dodefualt()
>
>nope, just what you see above. In the form instance its just 'default'
>
>Does this clarify?
>
>Harry

What version of VFP? There is a bug in 5.0 that would cause this. The fix was to add DODEFAULT().