>Hi BB
>
>No, not the combo. How can you assume what exact is for the combo? The code shown is for each of the text boxes. Yes Set Exact was different but I've been experimenting with either value (clutching at straws) and I don't think either makes any diference.
>
>In any case, I've tried every permutation of on/on, off/off, on/off, off/on for the two text boxes and no difference.
>
>The only code in the Operator combo is in the IRChange():
>
>Thisform.txtOperator.value = This.List( This.ListIndex, 2)
>
>Any other ideas?
>
>Cheers
>
>Terry
>
>>Terry,
>>I see that in TextBox Valid you set SET EXACT ON, but in Combo SET EXACT is OFF, what happens if you change both to be OFF?
>>
>>
>...

:o)))
Because I saw this comment for second code:

* Code for Text Box .Valid() for Family - Char data - OK
* _________________
LOCAL	lcExactSet

lcExactSet		     = SET( "Exact")
Set Exact On

and assumed that first code is for combo.


Check to see if this will resolve the problem:

* Code for Text Box .Valid() for Operator - Numeric key val - the problem
* _________________
LOCAL	lcExactSet
LOCAL lnValue


***************************
*** Assuming that field is integer (no fraction)
lnValue = INT(this.Value)

lcExactSet		    = SET( "Exact")
Set Exact Off
If not INDEXSEEK( m.lnValue, .T., "OPERATOR", "CODE")	&& If not find this Operator no in Operators table
    = MESSAGEBOX(	"Sorry, Operator " + ALLTRIM( STR( This.Value)) + " does not exist.", ;
		MB_ICONSTOP, "Operator does not exist")
    With Thisform
      .cmdPreview.enabled   = .F.
      .cmdPrint.enabled	    = .F.
    EndWith 	  	  
Else
    With Thisform
      With .cboOperators
	.Value 		    = m.lnValue
      EndWith 
      If  .lValidStart;
      and .lValidEnd
          .cmdPreview.enabled  = .T.
          .cmdPrint.enabled    = .T.
      EndIf
  EndWith
Endif
Set Exact &lcExactSet