>The !! is in a picture clause which has a control code for each character position meaning there are two characters, both forced to upper case.
>
>The last two functions looks like they are referencing varaibles for the definition
>
>Can't help you with the middle question, if nobody else chimes in I will dig out my older reference manual tonight and look it up.
>
>Bob
>
>
>>What is the "!!" in the first GET for? One "!" would convert to upper, but why two?
>>
>>I can't figure out what the ";" is for in the second button.
>>Or what the "IV" portion of the PICTURE is doing.
>>
I think the second one creates a set of invisible buttons. They are one character wide and max_view-1 lines long. But it's been a while for me too and I don't have any documentation handy.






>>The FUNCTION in the last two don't seem to match the codes in the help. What would "pupdhe" and "pdae" be for? Are the variables maybe?
>>
>>
>>

>>@ 03 * row_incr + row_plus, 58 GET new_rem ;
>>	PICTURE '!!' VALID v_find( .T. )
>>@ 08 * row_incr, 02 GET choice ;
>>	PICTURE '@*IV ' + REPLICATE( ';', max_view - 1 ) ;
>>	SIZE 1, 76, 0 ;
>>	WHEN rem_cnt >= _CUROBJ - 1 ;
>>	VALID pullrem()
>>@ 02, 02 GET choice ;
>>	FUNCTION pupdhe;
>>	SIZE but_height, but_width, 1 ;
>>	VALID rec_rem() ;
>>	DEFAULT( 1 )
>>@ 03 * row_incr + row_plus, 02 GET edit_del ;
>>	FUNCTION pdae ;
>>	SIZE 1, radio_width, 1 ;
>>	VALID v_edit_del() ;
>>	COLOR ,,,,,,,,&control1_color,&disabl1_color
>>