>If you call FSIZE() with a field that does not exist, it returns 0, rather than throwing an error. Although, I suppose, MS could argue this is "by design".
>
>So, watch out for typos with FSIZE().

It's been posted here a couple of time that I've seen as a way to check whether a field exists instead of parsing the AFIELDS() output.

Also, take note that FSIZE() returns different information depending on SET COMPATIBLE. If it's OFF (default) then it returns field information. If it's ON, then it returns the size of files (which is a very quick way to find the size of files and not parse the ADIR() output).

< snipped >