[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index] [Date Index] [Thread Index]
[SQR-USERS Info] [SQRUG Home Page]

Re: Let versus Move



Joe,

There isn't any reason to do let and move to the same variable.  There's just
many ways to do the same thing in SQR.  For instance, let #x = #x + 1 is the
same as add 1 to #x.

Regards,
         Jay Chin

PeopleSoft Integration Services / IBM Global Services
Voice  (301) 803-2799
Fax      (703) 237-9635


Joe <jejohn1216@SURFREE.COM> on 08/27/99 11:12:21 AM

Please respond to SQR-USERS@list.iex.net

To:   Multiple recipients of list SQR-USERS <SQR-USERS@list.iex.net>
cc:
Subject:  Let versus Move





Greetings, SQRUG

I inherited an SQR that has the following code in a procedure called
get-timelines:

 let $firstline = 'Y'
 let $tl_cust_id = ' '
.......
 let #pbill_tot_fee_expense = 0
 let #pbill_tot_oth_plcmnt_exp  = 0
.......
 move 0 to #pbill_tot_oth_plcmnt_exp
 move 0 to #pbill_tot_fee_expense
.......
begin-select
.......

I know the procedure is to set values to 0, but I don't see why you need to do
Let and Move to the same variable.

SQR Server Manual says that:
LET assigns the value of an expression ('0') to a string/numeric/date variable,
and that
MOVE moves one field ('0'?)to another field and provides the option of edits to
the field.

Can someone explain this to me?

As Always, TIA

Joe Johnson


~~ JEJ ~~   ;{)

__________________________________________
$14.95 a month Unlimited Internet Access.
Get your first month for $1.00.
http://www.surfree.com/promo