Re: Net.data START_ROW_NUM with SELECT WHERE clause

Hi Anton,

Thanks for the tip -- I actually got bit by that during the course of this.
I set RPT_MAX_ROWS to "20", and it worked as expected where I was looking,
but someone else noted that it also limited another result set where I did
not want to limit it.

However, none of the above were my immediate problem. In the interests of
trimming the sample code I posted, I left out the offending piece:

http://xyz.com/cgi-bin/netdatamacros.dtw/macro1?ACCT=&NAME=test&MR#=&START_R
OW_NUM=21)

The problem was the variable name "MR#".  Net.Data appears to have ignored
everything past the "#".  When I tried it with a value for MR#,

http://xyz.com/cgi-bin/netdatamacros.dtw/macro1?ACCT=&NAME=test&MR#=abc&STAR
T_ROW_NUM=21)

and showed the field values in an HTML block

%HTML (xyz) {
    MR# = $(MR#)
%}

it did not show the "abc" as expected.  I changed the field name to MRNbr
and all is well.

Thanks to all who responded!

Peter Dow
Dow Software Services, Inc.
909 793-9050 voice
909 522-3214 cellular
909 793-4480 fax


----- Original Message -----
From: "Anton Gombkötö" <gombkoetoe@ASSOFT.COM>
Sent: Tuesday, August 20, 2002 7:12 AM
Subject: RE: [WEB400] Net.data START_ROW_NUM with SELECT WHERE clause


The example at ignite400 uses START_ROW_NUM and RPT_MAX_ROWS as global
variables.

So you have the effect of paging activated for other selects, too.

To avoid this, you could keep the values in variables with other names and
use them only locally in the SQL function:

@ListPage1(mySTART_ROW_NUM, myRPT_MAX_ROWS)

%FUNCTION(DTW_SQL) ListPage1(IN START_ROW_NUM, RPT_MAX_ROWS) {