Steve, what is the value of 'This.Value' when it's not populated? And is there an 'On Error' routine running? Also, if the value of the field is an empty date, I wonder if the fact that Date() - {} = 0 is causing a problem.

Alan

>I thought of that, too. Strictdate is set to 0 during the valid procedure. I can step through the procedure; it stops responding immediately after exit. The trace screen shows the prg line that calls the screen (do form xxxx), which I think is appropriate.
>I can hit the cancel button in the trace window....otherwise, I can't use any keyboard strokes in the trace window either. I don't think there would be any strange on keys....
>
>
>>Any set date commands in your app? if you put 'set step on' in the gotfocus of the text box or at the beginning of the valid event and verify the value of the textbox before you check it's integrity in your valid event, what is the format of the date entered? Is set strict date on?
>>
>>Tracy
>>
>>>I have a form which was just converted from FPW/2.6 to VFP 6. The modal form works fine, I've moved all code into the appropriate methods. However, one field freezes (or appears to freeze) if there is a condition that causes the valid to fail. the controlsource is a date memory variable. On this form, if the date is within the valid parameters upon exit, then the focus moves to the next control as expected. the form only dies when the following code is tripped.
>>>
>>>Here's the valid code:
>>>

>>>if date() - this.value > 365
>>>     return .f.
>>>endif
>>>

>>>
>>>This works fine if I populate the variable, then run the form from the command line, so I assume there is some wierd setting this old app might be tripping.
>>>
>>>any ideas would be greatly appreciated!