JM THe workaround I posted was for DOS, not Windows. In windows, the best solution I've seen is the one with the period as a substitute.
David Blocker ----- Original Message ----- From: "J.M. GRATIAS" <[EMAIL PROTECTED]> To: "RBASE-L Mailing List" <[EMAIL PROTECTED]> Sent: Saturday, June 14, 2003 7:12 AM Subject: [RBASE-L] - Re: Difference in way 1.864 works David, Karen : > Cho vrn from #values for ((LJS((CTXT(OurNum)),6)) &+ (LJS((InsuredLName + ',' & InsuredFName),25)) &+ (LJS((ClaimantLName + ',' & ClaimantFName),25)) &+ (LJS((IFNULL(LossDate,'����������',(CTXT(LossDate)))),10)) + & (RJS(CompNo,3))),OurNum + from Incident where &vwh at Center Center Title + 'OurNum_Insured________________Claimant________________DateLoss_Comp' The wierd characters in the fix - (IFNULL(LossDate) etc. are CHAR 255 characters. That fixed the problem. < This workaround is not acceptable for me: in my case, the ugly spurious char display into the CHOOSE windows in both 1.851/1.866 versions. Changing to a point (IFNULL(LossDate,'.',(CTXT(LossDate))) works, but it is not very nice .... I looked an other char that display like a space, but which is not consider as NULL by RBW. Seems that CHAR(160) to the trick ... Did anybody found any other changes in the way 1.866 handle NULL variables in functions ? Best regards, J.M. GRATIAS, Logimatique
