• Subject: RE: Hex '00' to Hex '40'?
  • From: "Stone, Brad V (TC OASIS)" <bvstone@xxxxxxxxxxxxxx>
  • Date: Thu, 1 Jul 1999 11:01:47 -0500

Ok, here's more for the story.

The web front end is using cold fusion.  On the web form, there are 3 fields
for item numbers that the user can enter in.

They enter an item number in the first field, but leave the other two blank.
These last two fields when mirrored from the SQL database to our AS/400 are
the ones causing the problems (coming across as X'00').

The SQL database is set up to have a default null value for the columns, but
since they are filling these columns from a web form, whatever was in the
form is inserted into the column.

To me, this doesn't make sense.  When I read standard input using CGI, if
the field is blank, the field is blank (x'40').  Blanks should not have a
problem transferring through data mirror.

So, here is what I figure is going on..

The field is not null (X'00')
The field is not blank (X'20') or (X'40') 

i have no idea what the hex value of the field is in the SQL database before
it comes over.  I talked to the programmer and he said it's blank.  Now, I'm
guessing he doesn't mean blanks, but just empty.  So if you copied it to a
CSV file, three text fields, one with a value and two blank, would look like

instead of


Or would it be the other way around?

Does this help?  
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

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

This mailing list archive is Copyright 1997-2019 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].