<< It seems like just recently that doesn't work -- it instead prints a blank report to a PDF that is emailed out. It creates a PDF file that cannot be opened. So I had to change my code to check for data first, before the report prints. Makes me worry about code I have elsewhere. I could have sworn an error code used to be generated ... >>
Glad to know it's not just me. I'm currently working around this problem here (fortunately, most of my report printing is done by calling a single PRINTRPT procedure, so I have to make a limited number of changes). But my bigger problem is that sometimes this seems to happen even when I believe the report _does_ have data — and if you restart R:Base and let the same procedure run, it does produce data. I'm currently working to centralize all my direct-to-PDF printing so I can check the file size _after_ the report is generated and at least avoid sending the empty files (and notify the admin, who can restart the system and get the correct reports). I'm sure this must be something I'm doing — not clearing variables, not closing some programming structure, or something. But no errors are generated, and after you start R:Base it seems to be a very random period of time and set of operations before the problem is seen. Sometimes right away, sometimes not at all, sometimes after a few hours. . . -- Larry
