Re: [WEB400] Net.data START_ROW_NUM with SELECT WHERE clause

["Peter Dow" <maillist@xxxxxxxxxxxxxxx>]

Hi Zak,

Thanks, I tried your suggestion, but it didn't work. My understanding was
that RPT_MAX_ROWS and START_ROW_NUM are globally defined by Net.Data, so I'm
a little puzzled as to why I have to define them.

The other odd thing is that I'm passing START_ROW_NUM in as a parm from the
URL (e.g.
http://xyz.com/cgi-bin/netdatamacros.dtw/macro1?ACCT=&NAME=test&START_ROW_NU
M=21), so it's defined there, just as ACCT and NAME are.  And parms passed
this way are global, at least I've been able to use ACCT and NAME in all
macros without having them defined globally.

I put in some HTML to show the values of START_ROW_NUM and RPT_ROW_MAX at
the beginning of the macro1 HTML section and they both are empty strings, in
spite of the URL.  I think the problem is the limit on the size of a URL vs
data submitted via form, but I can't remember the limit.

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







----- Original Message -----
From: "Metz, Zak" <Zak_Metz@G1.com>
Sent: Tuesday, August 20, 2002 12:23 PM
Subject: RE: [WEB400] Net.data START_ROW_NUM with SELECT WHERE clause


> At a glance, I believe the problem you're having is that START_ROW_NUM is
> going to get set to "1" every time the page is loaded because of it being
a
> global variable. Instead, add code like:
>
> %IF(START_ROW_NUM=="")
>   @DTW_ASSIGN(START_ROW_NUM,"1")
> %ENDIF
>
> ...in your %HTML(macro1) block so that it doesn't get reset inadvertantly.
> You'll need to pass the variable to your SQL block since it won't be
global
> anymore.
>
> HTH...