>>>>>I created a cursor. I did some additional processing after that cursor was created. Now there's a column I don't need anymore.
>>>>>
>>>>>How do I get rid of that column?
>>>>>
>>>>> I tried the following
>>>>>
>>>>>ALTER table NameOfCursor drop column NameOfColumn
>>>>>
>>>>>Didn't work.
>>>>>Error 1115 : Invalid operation for the cursor.
>>>>>
>>>>>Is the only solution creating another cursor and selecting only the needed columns from the original cursor?
>>>>
>>>>
>>>>The reason why you cannot is : the cursor contains a field with a name longer than 10 chars
>>>>
>>>>See message#1459597
>>>
>>>I was about to post similar response. I got burned on that one myself.
>>>Normally I never use field names longer then 10 chars. Problem was that I had one of those to be 11 - entered by mistake.
>>
>>
>>
>>> Normally I never use field names longer then 10 chars
>>Then this is worth looking at
>
>It is indeed enjoyable/relaxing light weight read but I do not understand how it is related to
>using long field names (and all the problems associated with it) within VFP ?
>
>I support 100% long and descriptive Procedure/Class/Method/Variable names in vfp but I am
>AGAINST using long field names in VFP. For simply practical reasons nothing else.
>Who ever used/uses local cursors extensively, must have already or sooner/later WILL experience
>one problem or another. As you sure know, long table names are latecomers in xbase / VFP world, so I am not sure that
>all VFP commands/functions are 100% updated/debugged to properly process them.
>Create Cursor / alter table alias() is one example.
>
>I had few other problems with them as well, but cannot exactly remember context.
>However I am sure there are more. Perhaps our more experienced/knowledgeable VFP community members
>can list out few more commands/contexts where you will run into problems with long field names.
>
>Do you think that using field names longer then 10 chars is wise thing to do ?
>If so, please elaborate why.

Trying to squeeze a name in 10 chars may give cryptic results/names - more difficult to remember what the field contains - more difficult to read/understand sql statements