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 .....
At 11:17 AM 6/12/2003 EDT, you wrote:
>
>I upgraded a client to version 1.864 of RBWin from the
>early 1.842 that they were using and ran into a
>difference in the way the choose command works. I had a
>menu like this:
>
> CHOOSE vAsk FROM #VALUES FOR ( +
> LJS(CompanyName,25) & LJS(city,12) & LJS(State,4) ) +
> FROM companies WHERE .....
>
>In version 1.842, if 'City' was null, it would preserve the
>space and the 'State' would appear in the last column under
>the other states.
>
>But in version 1.864, if City is null but State is not, it
>moves the state over into the City column! Has anyone else
>noticed this? I tested this through version 1.851 and it
>operates the old way. So somewhere after 1.851...
>
>So you would have to test EVERY column that might be null
>as follows. You'll notice the period in the IFNULL formula;
>if you put a space, it leaves out anything that follows that
>column, so you must apparently put a placeholder in there of
>some kind.
>
>CHOOSE vAsk FROM #VALUES FOR ( +
> LJS(CompanyName,25) +
> & LJS( IFNULL(def_value,'.',def_value),20) +
> & LJS(State,4) ) +
> FROM companies WHERE .....
>
>
>I'd love to know I did something wrong....
>
>Karen
>
><HTML><FONT FACE=arial,helvetica><FONT SIZE=2 FAMILY="FIXED" FACE="Courier
New" LANG="0"><BR>
>I upgraded a client to version 1.864 of RBWin from the<BR>
>early 1.842 that they were using and ran into a<BR>
>difference in the way the choose command works. I had a<BR>
>menu like this:<BR>
><BR>
> CHOOSE vAsk FROM #VALUES FOR ( +<BR>
> LJS(CompanyName,25) & LJS(city,12) &
LJS(State,4) ) +<BR>
> FROM companies WHERE .....<BR>
><BR>
>In version 1.842, if 'City' was null, it would preserve the<BR>
>space and the 'State' would appear in the last column under<BR>
>the other states.<BR>
><BR>
>But in version 1.864, if City is null but State is not, it<BR>
>moves the state over into the City column! Has anyone else<BR>
>noticed this? I tested this through version 1.851 and it<BR>
>operates the old way. So somewhere after 1.851...<BR>
><BR>
>So you would have to test EVERY column that might be null<BR>
>as follows. You'll notice the period in the IFNULL formula;<BR>
>if you put a space, it leaves out anything that follows that<BR>
>column, so you must apparently put a placeholder in there of<BR>
>some kind.<BR>
><BR>
> CHOOSE vAsk FROM #VALUES FOR ( +<BR>
> LJS(CompanyName,25) +<BR>
> & LJS( IFNULL(def_value,'.',def_value),20) +<BR>
> & LJS(State,4) ) +<BR>
> FROM companies WHERE .....<BR>
><BR>
><BR>
>I'd love to know I did something wrong....<BR>
><BR>
>Karen<BR>
></FONT></HTML>
