>>Ok,
>>
>>two remarks
>>
>>(1) Yes, that one is shorter. I take it that you handle the INSERT in another part of the code, although it can easily be added here
>>
>>(2) Field(n) returns upper, watch the collating sequence
>>

>>CASE INLIST(FIELD(m.lnPos), "cLast_Updated_User", "tLast_Updated_Date")
>>

>
>We don't need them for inserts, because we have two different fields tEntered_Date and c_Entered_User, e.g. we keep track of insertion and modifications in table. We also do foxaudit(), so these fields seem a little bit redundant.
>
>I caught the second part, you're right.


So, where are tEntered_Date and c_Entered_User handled then ? In foxAudit() ?