I see - Yes, you're exactly right. In fact the code in VM is something like

IF lReturn = .F.

So I'd have to check all the validation in all the VM base controls, and frankly I just haven't made the time.

Barbara

>Just guessing that the return is sending the value back to the parent method in VM and not being checked for data type. No other reason other than to confirm that the problem is not really the validity of returning 0.
>
>>Sure would - why?
>>
>>
>>>Would that be a data type mismatch error?
>>>
>>>>Unfortunately in at least one framework (Visual MaxFrame) return 0 leads to an error so I've been using Return .F. until I can rewrite the base VMF code. One of those "Damned if you do, Damned if you don't" affairs.
>>>>
>>>>>return .f. could generate a VFP error message. Use return 0 if you want the current control to retain focus.
>>>>>