What's wrong with one these options:

1. Hardcoding
2. Put #DEFINE T_VARCHAR "V" in your own standard.h file invoked AFTER foxpro.h
3. Add #DEFINE T_VARCHARFABIO "V" in foxpro.h

2. is my favourite. BTW, I never #include foxpro.h, I have my own standard.h which include only the constants I really need, including constants for other programs I use frequently. (Did someone mention that include is not only a reserved word in VFP, it is also a very frequently used word) <s>

>>Hi Fabio,
>>
>>first of all, documented behavior is not a bug...! But, I also agree that it is not logical to let different field types give the same return value when it should be easy to give different values.
>>
>>My guess is that since TYPE() and VARTYPE() mostly is used to check memory variables and properties, and not fields, it was low priority. Personally I ALWAYS use AFIELDS() for fields, I even wrote a FIELDTYPE() function many years ago, as a part of my standard function library.
>>
>
>Well,
>then try to use the FoxPro.h T_VARCHAR definition with AFIELDS().
>
>Fabio