>>Don't forget the standard warning about SET EXACT. With SET EXACT OFF values like "RAMA","JOHNNY" become "RAM" and "JOHN" for comparison purposes and could return an incorrect TRUE. That may be OK in the application, but then again................
>
>Rich,
>Alltrim(THISFORM.COMBO1.Value) was used to force exactness. RAMA,JOHNNY are not on list.
>PS: Inlist was buggy however as Hugo pointed out.
>Cetin

Maybe I wasn't clear about where the "RAMA" and "JOHNNY" might be.

SET EXACT OFF
? INLIST(ALLTRIM("RAMADA"),"RAM","JOHN")
? INLIST(ALLTRIM("JOHNNY"),"RAM","JOHN")

Both of these return TRUE. That may or may not be correct in the context of the application. If it should be false, then a SET EXACT ON is required.