that makes a lot of sense.
let me look into that.


>Edgar, Just a shot in the dark but could it be that the browse window definition has been stored by VFP in foxuser.dbf and it now uses the "old" browse window definition?
>
>>mmm..
>>I don't know if I follow you.
>>Like I told Steve, padding the field on the SELECT works, so now I have 40 char long, but the "display" when I browse(and that is only when selecting to the cursor) keeps the traing spaces. I would thing is reasonable if it would bring "some" trailing spaces but like it is right now is like it did not pad anything at all.
>>
>>
>>
>>>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