Hi Sylvain,

In your first post on this you stated that the field involved with the FOR *does* exist in the destination table.

That didn't seem right to me so I checked Hacker's Guide and it says does *not* exist....
Now, here, I see you also write **not exist**.

I wonder if this thread might have taken a different turn if your first had said NOT?

Cheers,

Jim N

>AFAIK, this "feature" only affect appending from a table, where the field on which the FOR part is based do not exist on the destination table.
>
>>I have not experienced that! When I have run APPEND FROM with a FOR clause, it has worked correctly. For example, I used the following code to create a cursor of the Procedure/Function and Parameter statements from one of my procedure files:
>>
>>CREATE CURSOR Prg (Line C(254))
>>APPEND FROM Mc_procs.Prg TYPE SDF ;
>> FOR UPPER(LEFT(ALLTRIM(prg.line),4))=="PROC" ;
>> OR UPPER(LEFT(ALLTRIM(prg.line),4))=="FUNC" ;
>> OR UPPER(LEFT(ALLTRIM(prg.line),4))=="LPAR" ;
>> OR UPPER(LEFT(ALLTRIM(prg.line),4))=="PARA"
>>
>>Perhaps using a cursor as the destination or the TYPE SDF has some effect, I don't know. Do you name the destination alias in the FOR clause that fails?? (BTW, I got help creating this code from Christof Lange)