Larry, no suggestions -- just glad you noticed the same thing I did. I had code that printed a report to a PDF, and I would check the error variable afterwards and give a message if no report printed. 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 ...
Karen > 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
