Re: LOVAL /HIVAL in SQL

Hmmm. Looked through some more examples and it looks like I can drop the apostrophes around the *HIVAL *LOVAL 's. I thought they were constants but they are "magic" values it seems!

So it now looks like this and it works (snippets):

D q S 2A Varying
D Inz('''')

/free
if actcode<> *blanks;
act1 = q + actcode + q;
act2 = q + actcode + q;
else;
act1 = *LOVAL;
act2 = *HIVAL;
ENDIF;
exec sql
select * from myfile where
myfield between act1 and act2;

Subtle but important.

Thanks,

Pete


Michael Daly wrote:

Pete,

*LOVAL and *HIVAL are specific to RPG only. The represent the lowest, and highest, respectively, possible value for the field to which they are applied. To duplicate their function in SQL, "act1" would need to be set equal to the lowest value allowed for the type of field "myfield". Likewise with "act2", the highest value allowed.

Michael

I came across the trick of using the BETWEEN OPCODE in embedded SQL
statements and it looks like a great way to handle multiple variable
select statements. However, I can't get it to work, even with
interactive SQL. The interactive SQL looks like this:

select * from myfile where
myfield between '*LOVAL' and '*HIVAL'
myfield is a character field. If I don't use the single quotes, I get
a runtime error "Token * was not valid." If I do use the quotes it
runs but I get no output.

In my RPG I have (snippets):

D q S 2A Varying
D Inz('''')
/free
if actcode<> *blanks;
act1 = q + actcode + q;
act2 = q + actcode + q;
else;
act1 = '*LOVAL';
act2 = '*HIVAL';
ENDIF;
exec sql
select * from myfile where
myfield between act1 and act2;
That statement, with *LOVAL/*HIVAL should return me all the records,
but it returns nothing. What is the proper syntax? What have I
missed?

Pete Helgren