>>I make the headers of each grid column clickable to set the order for searching. By default, my grid class sets orderable columns to blue foreground and the currently ordered column forecolor in red. I have 3 properties of the grid: 1 for tablename to search, the order tag to use and the fieldname to search. I have a custom method of the grid that is called by the click events of the column headers. I pass to the method which column number was clicked. I then set the column header forecolors, change the table order, etc. You will have to have additional logic to handle switching of tables as well.
>
>Thanks, but because grid may change the recordsource means no fix header will
>sure be Order Tag, even I copy the CDX() example and modify some.
>I cannot use Alen() to get the array size of tag. ~_~'

Yes, but you can use a case statement in the click of column header:

Do case
   case alias() = "TABLE1"
   case alias() = "TABLE2"
endcase

>
>

---

>>I then can use an incremental search textbox that also has custom properties of the table, index tag, etc., to use in the search. Since I have a fieldname property, when my incremental search textbox is used I can test the field type using the type() function.
>
>Um... I have download the QUickfill in File Section, but the perform will poor
>for 20K data. So, I drop it and use basic locate
>

I will e-mail you my incremental search class for you to test.

>>LIKE is strictly for SQL statements. You can issue:

>>     Locate for "someval" $somefield

>>which will return records with *someval* anywhere in *somefield*
>
>Because I am afraid the user want something in middle.
>Like '%FC__12%'....
>
Locate for "someval" $somefield works exactly like the SQL example:

Like '%FC_12%'