Does anyone know a method for using SET NODATA on a Reporting Object?

We are usings WebFOCUS 7.6
Windows XP

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

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. 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

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.

Variable length fields(AnV) could be part of the issue:

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

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.

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).