>>OK, I ensured that they weren't > 10 chars wide. First they were called csrWatever.NumPass1 and csrWatever.NumPass2 (both identical numeric fields). So I changed them to Num1Pass and NumPass, but still I can't get past the problem.
>>
>>In between, I deleted the fields froom the report and all the remainder of the fields were allowed, and the report previewed OK.
>>
>>FWIW the fields are numeric 16.0 (that's what they ended up as from the following SQL:
>>
>>

>>SELECT ET.Operator, ET.Route, ET.Class, ET.Date, op.Desc as OpDesc, ;
>>	SUM(IIF(BETWEEN( ET.date, ldStart1, ldEnd1), Number, 0000000)) AS Num1Pass, ;
>>	SUM(IIF(BETWEEN( ET.date, ldStart2, ldEnd2), Number, 0000000)) AS Num2Pass ;
>>...
>>

>>
>>ANy ideas?
>
>I saw that the problem has gone away, but fwiw, you have Num1Pass and Num2Pass in the query and you talk about NumPass1 and NumPass2.
>
>Tamar

Hi Tamar

Ha ha! That was because I feared that VFP may be having problems distinguishing cursor fields that are identical all but the last char (although I hadn't reached the 10 char uniqueness sig figs - so I was clutching at straws) so I changed their names to try if that worked. I'd changed the code but forgot to change the names in the message.

That's what I think! :-)

Terry