I think the value is padded out when going to a cursor field because the field length must be a fixed length and VFP must guess what the maximum possible length of that field might be no later than when the first record arrives. The maximum potential length of the result field is the total length of the component fields, so it pads the field out to that length. This seems like reasonable behavior to me.

...Jim