Thanks Sergey,

I had deleted the object and added a new one to replace it and that solved the problem.

I would love to know how the PICTURE clause got in there, maybe this was available in earlier versions of the Fox and this report was converted from that version?

>Yes, that the one that causes the problem. Open report as a table and blank out the PICTURE for that field.
>
>>what I tried was delete the offending object and add a new one... and that works! So it's definitely something strange on that object.
>>
>>I used VSS to do a diff on the old report with the bad object and the new one. here is what it says was deleted:
>>
>>[UNIQUEID] _RFI0OOWKO
>>[OBJTYPE] 8
>>[START EXPR]
>>content[END EXPR]
>>[VPOS] 31042
>>[HPOS] 46667
>>[HEIGHT] 1875
>>[WIDTH] 30938
>>[PICTURE] "@T"
>>[START COMMENT]
>> [END COMMENT]
>>[FILLCHAR] C
>>[FILLRED] 255
>>[FILLGREEN] 255
>>[FILLBLUE] 255
>>[FONTFACE] Arial
>>[FONTSIZE] 10
>>[MODE] 1
>>[FLOAT] .T.
>>[STRETCH] .T.
>>[RESETTOTAL] 1
>>[SUPALWAYS] .T.
>>[SUPRPCOL] 3
>>
>>[ RECORD]
>>[PLATFORM] WINDOWS
>>
>>The interesting line there is the [PICTURE] "@T" one, I don't know if that is what is causing the problem, but I can't see a way to set a picture clause on an object.
>>
>>Thanks.
>>
>>>>Not at the moment. The reports are on a computer in France and the owner of the computer has shut down for the night. I'll speak with them tomorrow, get permission to send the files and get the files to you.
>>>
>>>One simple thing to try before that: copy the object from the report that works into the report which doesn't, and just retype the expression. You might be just lucky.