I would agree to a point with Bob's "should" rule simply
because it should emphasize Rule #1.  :)  

Brad
www.bvstools.com

On Tue, 26 Apr 2005 16:17:35 -0500
 "Bob Cozzi" <cozzi@xxxxxxxxx> wrote:
> Day 1, class 1, hour 1, Rule 1, of HTML, always never use
> spaces or strange
> character (i.e., /) in your HTML form field names when
> working with the
> AS/400. Form field names _should_ match your field names
> in your CGI RPG
> program whenever possible: "should".
> 
> -Bob Cozzi
> www.RPGxTools.com
> If everything is under control, you are going too slow.
> - Mario Andretti
> 
> 
> -----Original Message-----
> From: web400-bounces@xxxxxxxxxxxx
> [mailto:web400-bounces@xxxxxxxxxxxx] On
> Behalf Of Shane_Cessna@xxxxxxx
> Sent: Tuesday, April 26, 2005 1:58 PM
> To: Web Enabling the AS400 / iSeries
> Subject: RE: [WEB400] get vs post...
> 
> hey all,
> 
> I figured it out...my zhb procedures didn't like a space
> in the <input> 
> tag name value...so, anything like <input type="text"
> name="Y/N Ind 1"> it 
> wouldn't retrieve because of the space in the name
> portion...I took out 
> all the spaces and it works beautifully...
> 
> Shane Cessna  
> iSeries Programmer
> iSeries WAS Administrator
> North American Lighting, Inc.
> (618) 662-4483 x2776
> shane_cessna@xxxxxxx 
> 
> 
> -- 
> This is the Web Enabling the AS400 / iSeries (WEB400)
> mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/web400.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].