>On VFP9 binary VFP doesn't trim 0h0 and copy the hex syntax,
>and for a varchar is not trimmed also;
>but a char ( binary ) is trimmed and then ( before VFP9 )
>you cannot copy into a text a binary field.
>
>
>

>CREATE CURSOR test1 (f1 c(1),v3 V(3) DEFAULT 'v ',c3 c(3) DEFAULT 'c  ' NOCPTRANS ,q3 q(3) DEFAULT 0h0000 )
>APPEND BLANK
>COPY TO test1.txt DELIMITED WITH "" WITH CHARACTER "|"
>MODIFY FILE test1.txt
>

>
>I think that this is not a casual bug
>but an awkward attempt (of the team) to interpret the developer mind;
>as a CHAR(1) as flag is used, often a space can be meaningful
>and in data exchanges doesn't trim could simplify the operation.
>Vice versa, CHAR(N=2,3,...) hardly it is a flag,
>and therefore the team has thought of trim the field.
>
>But,
>who write a dev env it doesn't have to think about thing it can do.
>COPY is a copy, then if a field is SPACE(3) copy must put 3 spaces into the target.
>
>Fabio

Fabio,
I didn't understand. No problem. Maybe you meant sort of SDF.
Cetin