Focal Point Banner


As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.

Join the TIBCO Community
TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.

  • From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
  • Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
  • Request access to the private WebFOCUS User Group (login required) to network with fellow members.

Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.


Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] NODATA is ignored or doesn't apply to TX fields

Read-Only Read-Only Topic
Go
Search
Notify
Tools
[SOLVED] NODATA is ignored or doesn't apply to TX fields
 Login/Join
 
J.Hines
Platinum Member
posted
Has anyone else experienced this? I'm in 7.7.03, and I have a field coming from SQL Server (where it is defined as varchar(max)) and the master file is like so:
 FIELDNAME=MEMO, ALIAS=Memo, USAGE=TX50, ACTUAL=TX,
      MISSING=ON, TITLE='Memo', $


I have SET NODATA = '' but it seems not to apply to this field, even though the report will show the default period, and I've confirmed on comparison to the SQL Server data that the field is null in certain rows, but it will not change the period to an empty string.

I've even tried using a define field using
 DEFINE FILE V_STARCHART
TESTER/I1 = IF MEMO EQ MISSING THEN 0 ELSE 1;
END


but this results in the following runtime error:
quote:
(FOC148) ERROR IN USE OF 'IS MISSING'

This message has been edited. Last edited by: J.Hines,


Prod: 8.2.0.4 OS:Windows 10 Output:AHTML, Excel 2007+

The life of a designer is a life of fight against the ugliness.
 
Posts: 141 | Location: North Carolina | Registered: August 10, 2012Report This Post
prodrigu
Platinum Member
posted Hide Post
J.Hines,

Try using the below and see if it works.

  
DEFINE FILE V_STARCHART
TESTER/I1 = IF MEMO IS MISSING THEN 0 ELSE 1;
END


Prod: WebFOCUS 7.7.03: Win 2008 & AIX hub/Servlet Mode; sub: AS/400 JDE; mostly Self Serve; DBs: Oracle, JDE, SQLServer; various output formats
 
Posts: 121 | Location: California | Registered: June 19, 2008Report This Post
Rifaz
Guru
posted Hide Post
I assumed, you want to display as blank in place of null values..If so, try this with your NODATA
DEFINE FILE V_STARCHART
TESTER/I1 MISSING ON = IF MEMO EQ MISSING THEN MISSING ELSE 1;
END


-Rifaz

WebFOCUS 7.7.x and 8.x
 
Posts: 406 | Location: India | Registered: June 13, 2013Report This Post
J.Hines
Platinum Member
posted Hide Post
Thanks both of you. I tried similar things to that yesterday, and I remembered something running, but now, whether I use
MEMO IS MISSING
or
MEMO EQ MISSING

both return the same error as above.


Prod: 8.2.0.4 OS:Windows 10 Output:AHTML, Excel 2007+

The life of a designer is a life of fight against the ugliness.
 
Posts: 141 | Location: North Carolina | Registered: August 10, 2012Report This Post
David Briars
Master
posted Hide Post
The issue might be that the missing comparison cannot be translated into a NULL test, for TX (BLOB?) fields.

If so, you might want to try, creating a DEFINE field, and testing on it: 
NOTETXT/A8000 = MEMO;
TESTER/A1 = IF NOTETXT IS MISSING THEN '1' ELSE '0';

This message has been edited. Last edited by: David Briars,
 
Posts: 822 | Registered: April 23, 2003Report This Post
J.Hines
Platinum Member
posted Hide Post
quote:
NOTETXT/A8000 = MEMO; TESTER/A1 = IF NOTETXT IS MISSING THEN '1' ELSE '0';


That was a good idea, I was thinking about something like that but wasn't sure how to do it.

However, that's still coming out as all zeroes, even for the MEMO fields that are having a period put in them.

I also just tried this with a much simpler, non-SQL Server file by creating a master file from an Excel file using the Upload Data function, and when I changed the field to USAGE=TX50 and ACTUAL=TX, it exhibited the same behavior. It will do the period for missing fields, but won't take anything set in NODATA.

Sounds like it's probably time to open a case on this.

This message has been edited. Last edited by: J.Hines,


Prod: 8.2.0.4 OS:Windows 10 Output:AHTML, Excel 2007+

The life of a designer is a life of fight against the ugliness.
 
Posts: 141 | Location: North Carolina | Registered: August 10, 2012Report This Post
J.Hines
Platinum Member
posted Hide Post
Found this old post after lots more searching (it could certainly have had a better title):

varchar vs tx

Anyways, it appears that the TX format probably shouldn't be used anymore. I just wouldn't have known that because I used the server console to create the synonym, and that's what it picked, so I figured it must be right (silly me).


Prod: 8.2.0.4 OS:Windows 10 Output:AHTML, Excel 2007+

The life of a designer is a life of fight against the ugliness.
 
Posts: 141 | Location: North Carolina | Registered: August 10, 2012Report This Post
  Powered by Social Strata  

Read-Only Read-Only Topic

Focal Point    Focal Point Forums  Hop To Forum Categories  WebFOCUS/FOCUS Forum on Focal Point     [SOLVED] NODATA is ignored or doesn't apply to TX fields

Copyright © 1996-2020 Information Builders