Moral of the tale .... TRIM any numeric data fields BEFORE they are written .... and a TRIMB doesn't hurt on strings either !
Ross Ferris Stamina Software Visage an Evolution in Software Development >-----Original Message----- >From: [EMAIL PROTECTED] [mailto:owner-u2- >[EMAIL PROTECTED] On Behalf Of Buss, Troy (Logitek Systems) >Sent: Friday, 14 May 2004 3:35 AM >To: [EMAIL PROTECTED] >Subject: RE: [U2] SPACE character ignored > >What is really scary is: > >PRINT NUM(" 1") >PRINT NUM("1 ") > >Both yield 1 (true). > >This has resulted in MANY downstream data issues where input validation >worked (using the NUM function) yet further down the road, printing out >order qtys using masking or doing a locate statement of "1" in " 1" does >not work. > >This is in my opinion, a really BAD idea. > >I had to rewrite several sections of a 4GL to accomodate these differences >when porting some code to universe recently. > >I would hope in a future release this could be an option to return to >better compatibility and predictability. >------- >u2-users mailing list >[EMAIL PROTECTED] >http://www.u2ug.org/listinfo/u2-users > > >--- >Incoming mail is certified Virus Free. >Checked by AVG anti-virus system (http://www.grisoft.com). >Version: 6.0.682 / Virus Database: 444 - Release Date: 11/05/2004 > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.682 / Virus Database: 444 - Release Date: 11/05/2004 ------- u2-users mailing list [EMAIL PROTECTED] http://www.u2ug.org/listinfo/u2-users
