Karen
 
I found the example from my client:
 
  *(Removed when upgrade to 6.5++: does not left justify lossdate if null:     CompNo appears in the LossDate column if LossDate is NULL: replaced with new below

  Cho vrn from #values for ((LJS((CTXT(OurNum)),6)) &+
   (LJS((InsuredLName + ',' & InsuredFName),25)) &+
   (LJS((ClaimantLName + ',' & ClaimantFName),25)) &+
   (LJS((CTXT(LossDate)),10)) & (RJS(CompNo,3))),OurNum from Incident where &vwh at Center Center Title +
'OurNum_Insured___________________Claimant___________________DateLoss_Comp'
)
  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.
 
David Blocker
 
----- Original Message -----
Sent: Thursday, June 12, 2003 6:07 PM
Subject: [RBASE-L] - Re: Difference in way 1.864 works


Nope, replacing & with + doesn't make a difference.


Try using + instead of the &operator.  The rule for & is that it
concatenates blanks leaving just one.  I'm surprised the code below ever
worked at all.  Try

    CHOOSE vAsk FROM #VALUES FOR ( +
    LJS(CompanyName,25) + LJS(city,12) + LJS(State,4) ) +
    FROM companies WHERE .....



Isn't RBTI finished with releasing more patches of 6.5++?

>I suggest that you post it to RDCC.


Karen

Reply via email to