This link is to the ASCII chart. It says that a hexidecimal 0 is null: http://www.ascii.ws/images/ascii-chart.gif (unless, in database terms, it's something different). We did a SQL query "length(fieldname)" and it returned a zero length.
Currently, we are doing a work-around similar to what...
It seems to be returning a hexidecimal zero, but NODATA doesn't see this a a true null value. As I mentioned in the previous posting on Feb 27th, if a new record is created and no value is entered in a text field, NODATA sees it as a null. However, once the record is updated, NODATA isn't...
We've queryied the database outside of WebFOCUS and have confirmed that the values in the tables are not null and not a space. The MISSING attributes for all fields are set to ON (the default). We are using multiple one-to-many joins (left-outer joins in most cases).
When the variable...
The &GROUPBY variable is returning a space. The ERP data being accessed is stored in a Progress database. Is it possible that the fields are null when the records are created if no value is entered upon creation, but then through maintenance of the record, the null value is lost and replaced...
How can I get the SET NODATA command to work for a "grouped by" report? Here's a snippet of my code:
.....
SET NODATA = 'N/A'
.....
TABLE FILE QSACUS
SUM
DESCRIPTION
CNT.counter AS 'COUNT'
PCT.CNT.CTRLNBR AS '%TOTAL'
COST/D12.2CM
BY TOTAL HIGHEST counter NOPRINT
BY &GROUPBY...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.