>>>What do you think anout long fieldnames in a VFP-table?
>>>I heard it might cause problems, if the table is corrupt.
>>>Should I use long fieldname?
>>>
>>>Karsten Leven
>>
>>It's better to avoid this, just to eliminate fieldname cut-off 'surprises' when you move data (e.g. using COPY TO) to free tables.
>
>That's can happen, but may be outweighed by this consideration: When user's link to our vfp DB through ODBC, they see the entire field names. Thus it's possible to be much more descriptive with long names, so unknowledgeable users can better know what an element is. Long names are also helpful even to developers over time to recall exactly what an element is...of course, we are all required to use them here whether vfp or SQL Server :)

I wouldn't give unknowledgeable users to make any judgements based on field names (even long ones:). It's possible to utilize Field's Comment property to get something really descriptive.