>>>I always use m. for variables when it's required. But in this particular case we wanted to shorten and simplify the code. Otherwise I would leave my original code where I was testing for existance of the field and building Insert command as a text variable.
>>>
>>
>>remember EMPTY(FSIZE("FIELDNAME")) for testing for existance of the field.
>
>Why type("Table.Field") = My type is not better? I think FSIZE behavior depends on the environmental settings.

sure, SET COMPATIBLE, but if you set it to DB4
many commands would change behavior, not only FSIZE().

Then for me SET COMPATIBLE don't exists.