ok, but in 6.5 (Just tested), I can only get it to work when NOT using Parens an ONLY when there are two items. In this configuration, the second one is the value returned in the variable designated in the choose. If you have more than one comma, it will fail and if you add Parens, it will fail with Any commas. No Kiddin! It seems to be the same behavior in 6.5 as in 7.1 AFAICT..
Rb6.5++ 1.864RT03 ----- Original Message ----- From: "Victor Timmons" <[EMAIL PROTECTED]> To: "RBG7-L Mailing List" <[email protected]> Sent: Thursday, December 23, 2004 10:59 AM Subject: [RBG7-L] - Re: correcting data where there is a primary &foreign keys > Well it seems to work in 6.5++ just fine if you use the code i sent in the > first place. Javier code should work just fine also. But you must use & > instead of . I wish i had remembered to test it at home using 7.1 :( > > > On 23 Dec 2004 at 7:30, MikeB wrote: > > > neither will work.... Once you put the Parans around the cols, the parser > > expects an expression, so you have to put in + or & as appropriate along with > > any type conversions required by the expression... > > > > If you omit the Parens, you can't designate a Return Column value... > > > > > > ----- Original Message ----- > > From: "Alastair Burr" <[EMAIL PROTECTED]> > > To: "RBG7-L Mailing List" <[email protected]> > > Sent: Wednesday, December 22, 2004 7:26 PM > > Subject: [RBG7-L] - Re: correcting data where there is a primary > &foreign keys > > > > > > > It looks like your CHOOSE syntax is confusing R:Base: > > > > > > Presumably, you are trying to display the 3 values in your menu but > you > > > appear to be telling R:Base that the value after the comma is what you > want > > > returned - and you've got two commas. > > > > > > Try it this way: > > > > > > CHOOSE vCID FROM #VALUES FOR DISTINCT + > > > (CID,SSN,(LJS(FullName,35)) ) + > > > FROM PEOPLELIST + > > > WHERE SSN like .vSSN + > > > ORDER BY Debtor > > > > > > or > > > > > > CHOOSE vCID FROM #VALUES FOR DISTINCT + > > > (CID,SSN,(LJS(FullName,35)) ), RetCol + > > > FROM PEOPLELIST + > > > WHERE SSN like .vSSN + > > > ORDER BY Debtor > > > > > > if you want to return RetCol to your result. > > > > > > If neither of those work try replacing the two commas within the > brackets > > > with ampersands. > > > > > > Regards, > > > Alastair. > > > > > > ----- Original Message ----- > > > From: "Chris Szeto" <[EMAIL PROTECTED]> > > > To: "RBG7-L Mailing List" <[email protected]> > > > Sent: Wednesday, December 22, 2004 11:11 PM > > > Subject: [RBG7-L] - Re: correcting data where there is a primary > &foreign > > > keys > > > > > > > > > > The only difference is instead of the Choose command it starts with > > > > select. > > > > > > > > CHOOSE vCID FROM #VALUES FOR DISTINCT + > > > > CID,SSN,(LJS(FullName,35)) + > > > > FROM PEOPLELIST + > > > > WHERE SSN like .vSSN + > > > > ORDER BY Debtor > > > > > > > > SELECT + > > > > CID,SSN,(LJS(FullName,35)) + > > > > FROM PEOPLELIST + > > > > WHERE SSN like .vSSN + > > > > ORDER BY Debtor > > > > > > > > BTW, thanks for all the assistance with this. > > > > -----Original Message----- > > > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of > Lawrence > > > > Lustig > > > > Sent: Tuesday, December 21, 2004 11:21 PM > > > > To: RBG7-L Mailing List > > > > Subject: [RBG7-L] - Re: correcting data where there is a primary > > > > &foreign keys > > > > > > > > > I have tried this way and it still does not work. I'm using 7.1 > > > > though > > > > > so I'm not sure if that has anything to do with it. The single > wild > > > > > cards did not work either unfortunately. > > > > > > > > Chris, could you post the SELECT statement that DOES work for the > > > > purpose of > > > > comparison? > > > > -- > > > > Larry > > > > > > > > > > > > > > > Victor Timmons > Tiz's Door Sales, Inc > 425-258-2391 >
