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     Set NODATA in a Reporting Object

Read-Only Read-Only Topic
Go
Search
Notify
Tools
Set NODATA in a Reporting Object
 Login/Join
 
Jeff Elam
Silver Member
posted
Does anyone know a method for using SET NODATA on a Reporting Object?

We are usings WebFOCUS 7.6
Windows XP


Jeff Elam
WF 8 in Windows
 
Posts: 44 | Location: St. Louis | Registered: September 17, 2004Report This Post
susannah
Expert
posted Hide Post
edit the reporting object and in the OTHER section, (where your USE statements go), stick in your SET NODATA phrase, and anything else you might like...such as SET BYDISPLAY = ON



In Focus since 1979///7706m/5 ;wintel 2008/64;OAM security; Oracle db, ///MRE/BID
 
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003Report This Post
Jeff Elam
Silver Member
posted Hide Post
Thank you, Susannah. That does work--mostly. The only exception is that it puts dots in the first record displayed, rather than the NODATA value we assigned. We also can't seem to make it work with Excel 2000 (I know there are some documented issues with Excel 2000 and the NODATA option). Thanks, again for all of your help! I'm going to put in a case with IBI.


Jeff Elam
WF 8 in Windows
 
Posts: 44 | Location: St. Louis | Registered: September 17, 2004Report This Post
<kreycraft>
posted
Jeff. I'm having the same problem with my reports. I'm finding NODATA works for numeric and date fields, but not alpha. I found by setting MISSING=OFF on the field in the master file, it would display properly but I was no longer able to query against that field. Did you get a response from Support?

Ken
 
Report This Post
Jeff Elam
Silver Member
posted Hide Post
We haven't put in the case yet, because we were having some difficulty isolating the problem. Should put it in early next week. I would also like to point out that I see the same issue with reports written in Developer Studio. I don't see the same behavior as you do with dates--dates act exactly the same as character fields for us. We don't have any null numbers--they are populated with zeroes. I'll post more information when I hear something from IBI.


Jeff Elam
WF 8 in Windows
 
Posts: 44 | Location: St. Louis | Registered: September 17, 2004Report This Post
Piipster
Guru
posted Hide Post
Variable length fields(AnV) could be part of the issue:

http://techsupport.informationbuilders.com/known_problems/20132025.html


ttfn, kp


Access to most releases from R52x, on multiple platforms.
 
Posts: 346 | Location: Melbourne Australia | Registered: April 15, 2003Report This Post
Jeff Elam
Silver Member
posted Hide Post
We've migrated over to a 7.6 environment, and the issue is no longer present. We saw it on 7.1.3. Thanks for everyone's input.


Jeff Elam
WF 8 in Windows
 
Posts: 44 | Location: St. Louis | Registered: September 17, 2004Report This Post
<kreycraft>
posted
For us it was a problem with varchars. Once I removed the V in the USAGE, the NODATA worked properly (i.e. USAGE=A30, ACTUAL=A30V).
 
Report 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     Set NODATA in a Reporting Object

Copyright © 1996-2020 Information Builders