小弟在使用以下方法時,發現很奇怪的事情耶... const   def_FieldName: array[1..19] of String = ('CUS_NO','CO_NM','CUS_NM','DR_NM','DL_CD','OUT_DL',   'MOD_CD','CH_NO','EN_NO','CAR_NO','S_ADR_CD','S_ADR2','HO_TEL','CO_TEL','M_PHONE','LA_SA',   'ASK_CD','CUS_ID','IV_NO');    var j:integer;     check:Boolean; begin   for j := 1 to 19 do begin     if def_FieldName[j]=Name then begin  --> j 的值居然是從19,18,17..1 check :=true; break; end else check :=false; end; result:=check; end; 不解...不是應該從 1,2,3..19 嗎? 初學者出沒注意!!

------
I like DeBug

Watch j in debugger with optimization on? Because j is used only as a looping index and compiler does all the necessary mappings for you...

>>compiler does all the necessary mappings SORRY william 兄,這句話有點不解意思.. 初學者出沒注意!!

------
I like DeBug

Look at the following code:    

procedure TForm1.Button1Click(Sender: TObject);
var
    i: integer;
begin
    for i := 1 to 10 do begin
        Application.ProcessMessages;
    end;
end;

(1) snapshot from CPU window with optimization: (2) snapshot from CPU window without optimization: In 1, there are only dec, jnz compared to inc, cmp, jnz in 2. It is pretty clear that 1 is more efficient. Hence the compiler is smart enough in choosing form 1 for you. In you case, the compiler also knows about the constant array def_FieldName and j is used only as an index of it, thus it performs proper mappings and your checking should goes from 'CUS_NO' to 'IV_NO'.

哈...原來就是讀書時課本所說的一樣.. 我明白了..謝謝.william 兄.. 初學者出沒注意!!

------
I like DeBug