Re: block input


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Tom Fulton on January 03, 2013 at 14:36:41: Uploaded files: 1

In Reply to: Re: block input posted by Barbara Brazil on January 03, 2013 at 11:51:35:

Apologies for confusing you, that was certainly not my intention. Uploaded is a simple block input program like we have in our Order Entry programs. Compile this program as a Comet16 object. Run the program under Comet16 and input the value 'ABC' for work6a$ and 'DEF' for work6c$. You'll see a result that we've expected all along ( and by "all along" I mean going back to the early Q days ) in a block input - trailing blanks for the block are stripped. work6a$ will be length 6 and have a value of ABC followed by three blanks. work6b$ will have a length of 6 and have a value of six blanks. work6c$ will be length 3 ( nothing but blanks followed its value and they get stripped ) and have a value of DEF. work6d$ will be length 0 and have no value. Now run the program under Comet32 and input the same values. Each field has been set to the strip() of itself. This is an entirely different behavior. We have one end-user who has encountered this issue and we've gone into the program and changed our comparison ( if spcnbr$ ne 'six blanks here' then... was changed to if strip(spcnbr$) ne '' then... ).


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]