>Why do you recommend to NOT use long field names? The problem in this thread is not a good enough reason for me.
>
>>Since I never use long field names, and never have had the need for it the last 15 years, that is not any problem in my programs. I strongly recommend NOT to use long field names, I don't see any benefit at all. But needs may vary, of course.
>>

Thread #940269 sounds similar. But in real world app I had a need to use ALTER TABLE and support LFN. What I did was to create a temp dbc and select into a temp table that lives in that dbc (cursors are tables anyway).
Cetin