A few months ago I posted about a problem in which R:Base will, after a while, begin generating empty reports (appearing on the screen as a completely blank page and as a PDF that cannot be opened because it contains no pages at all). At the time, I was advised to change my SCRATCH setting code to use the new SCRATCH TMP setting in the CFG file.
I've done that, but the problem persists. It is not consistent or exactly reproducible (therefore, I can't reasonably report it to RBTI), but it is frequent enough to cause my users lots of headaches. Because many reports are generated by a "robot" process and emailed before a human sees them, some top execs occassionally get blank reports which have to be regenerated. Also, I've noticed a second, potentially related problem. Previously when I tried to print a report that really contained no data, I'd get the famous error 2059 No Rows Found. I could check the error status (or SQLCode 100) and tell the user there was nothing there to print. Now, however, if I try to print a report with no records found I _do_ see a report — the same empty report that occurs when my "problem" appears. I can recode to check for data _before_ printing the report, but that requires 1) code changes and 2) a potentially time consuming count (for highly processed views that take some time to return even COUNT = 1). Any suggestions? -- Larry
