>>>I don't see why afields()+ascan() is too much work. It's just a single expression, provided the checked table is already open under some alias. Field() == m.field checking is still the best and simple.
>>
>>it is cruel and unusal punishment for your enslaved CPU. The performance is not even in the same ballpark.

>Sorry but I don't understand what you mean.
Cetin,

it is not too much work for the developer, but the performance of this construct may be worse by a factor exceeding 100 compared to field(). If such checks are "routinely" done a couple of hundred times in framework code you will get a time lag large enough to perceive in "human time frame". And the CPU has to work full time for a couple of ms.

regards

thomas