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

["Peter Dow" <maillist@xxxxxxxxxxxxxxx>]

Hi Anton,

Just to be clear, this worked:

http://xyz.com/cgi-bin/netdatamacros.dtw/macro1?ACCT=&NAME=test&MRNbr=&START
_ROW_NUM=21

and this did not:

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

The only difference being the variable name, MR# vs MRNbr. I agree that it's
probably the HTTP server.  If I use the variable name MR# in a form,
Net.Data sees the value; but if I use it in a URL as above, Net.Data does
not see the value.

Regards,
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: Wednesday, August 21, 2002 2:22 AM
Subject: Re: [WEB400] Net.data START_ROW_NUM with SELECT WHERE clause


><snip>The problem was the variable name "MR#".  Net.Data appears to have
>ignored
>everything past the "#".

So the example you posted would have worked? :-)

Yes, there seem to be issues with the #. But not as you used it. Just avoid
# as part for variable names.

You can have anchors on a page to hop/scroll around on the same page or
navigate straight to a certain point.

Having a Net.Data URL, that would be
http://www.myserver.com/Net.Data/macro/section#anchor.

I thought adding parms with
http://www.myserver.com/Net.Data/macro/section#anchor?p1=x&p2=y
should work, but it didn't.

I guess it's not a Net.Data issue, i expect the HTTP to be guilty, but
maybe guilty to work according to rules.

I didn't go too deep into it as the <form>-workaround works here:

<form action="/Net.Data/macro/section#anchor">
<input type="hidden" name="p1" value="x">
<input type="hidden" name="p2" value="y">
<input type="submit">
</form>