There were no set ansi or other unusual SET statements. However the problem is solved with "set ansi off". If I understand this right, the "set exact off" which I had included, did not operate in the SELECT statement, and to get the equivalent behavior the "set ansi off" is needed. Would that be a correct interprutation of the situation? Apparently the ON value was inherited from another application which I had run but my users had not.

Thanks Sergey.



>What the differenece is? Check all the SET settings, in particilar SET ANSI.
>
>>Using the same data, the following code sequence produces different results in the design environment as compared to the runtime environment.
>>
>>

>>lparameters thisfield, fundscx, lnForecastYear, lnCurrentTIPYear
>>clear
>>set exact off
>>set Deleted On
>>sele tip
>>local lnThisrec
>>lnThisrec = recno()
>>***************** Step 1 get prior year expenses based on fisyear
>>sele * from ledger ;
>>	where fisyear < lnCurrentTIPYear and source = fundscx and deleted()=.f.;
>>	order by fisyear ;
>>	into cursor carryover
>>sum -amount * factor to net_prior
>>
>>

>>Any ideas on what might be causing this would be appreciated.