Marc, You won't be able to measure a difference in performance speed between the two approaches, so I'm with Karen and Dennis. When you want to modify this in 6 months, with separate commands you'll be able to make the change in a few seconds. With the nested levels, you're almost certain to have to study and fiddle for a while to make sure you get all your commas and parens in the right place, and don't break one of the other SRPLs.
Bill On Mon, Jan 12, 2009 at 11:07 AM, MDRD <[email protected]> wrote: > Karen > > The code is for my eyes only so as long as it works and I understand it > that is OK for me. > > Separate commands may be best in case one of the vars is null I can skip > that SRPL. > > Thanks > Marc > > > ----- Original Message ----- > *From:* [email protected] > *To:* RBASE-L Mailing List <[email protected]> > *Sent:* Monday, January 12, 2009 9:38 AM > *Subject:* [RBASE-L] - Re: SRPL limit? > > Wow! I have never embedded even 2 SRPLs together. I would not be able to > figure out what you're doing with this statement. Unless you're doing it > for for job security reasons, if you're interested in anyone else figuring > out this code, I would suggest separate SRPLs! If you're doing it as a > form or report variable and don't want to do multiple ones, then maybe a > stored procedure that you can CALL. JMO > > Karen > > > > Hi > > > > I am building form letters and need to do about 20 SRPL's. Is there a > better way or do I string 20 SRPL's together? > The example only has 5 SRPL's > > SET VAR vtext = (SRPL((SRPL((SRPL((SRPL((SRPL (.vxtext, > '[fname]',.vfname,1)), '[heshe]', .heshe,1)),'[himher]', .himher, 1)), + > '[xx1]', .vxxmpt1,1)), '[xx2]', .vxxmpt2,1)) > > > Thanks > Marc > > > >
