Larry, I am seeing the same thing. Have a series of reports based on multi-table (i.e., ID_Info, ID_Numbers, Demographics, and Family) views with a shared field (IDNum) that have worked every time for months. Now the same views simply come out blank even though I have done nothing to the views for a long time.
Single table views and reports work great every time. If existing multi-table views are edited back to single table (ID_Info), the view loads with data and that portion of the report prints the expected data while leaving the remaining data empty. Add a second table to that same view (with the IDNum as the shared field), the view comes out blank. Remove the first table, and the view loads with the second table. Put the first table back in and the view is blank. When building an entirely new view/report from scratch that same thing happens. Using V8 with yesterday's update. Is there some setting that drives multi-table views? All our single and multi table views/reports worked just great at a recent demo. Tom Frederick Elm City Center 1314 W Walnut Jacksonville, IL 62650 Off - 217-245-9504 Fax - 217-245-2350 Email - [EMAIL PROTECTED] Web - www.elmcity.org -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Lawrence Lustig Sent: Tuesday, July 22, 2008 7:59 AM To: RBASE-L Mailing List Subject: [RBASE-L] - Reports with no pages. I've recently started running into a problem in which reports which are expected to have data show up with no data generated at all -- just a blank page. This happens both with users in compiled 7.6, but an interactive user application and a robot application that generates and emails PDF reports. In the later case, the PDF gets generated but cannot be opened -- Adobe reports that the document contains no pages (and, in fact, the PDF file is only 2K and when opened with notepad contains no pages). The users appear to be properly connected to the database since they can see and edit forms, and so on. The robot process runs disconnected except when it has to fire off a report, so it always has a fresh connection to the database. I mention this because at first I suspected dropped connections on the network. The problem is not consistent, unfortunately. Some reports work all the time, some as little as 80% of the time. In general, restarting the application seems to allow the report to run. This is a new problem since 7.6 and I'm wondering if some syntax requirements have tightened up, or if 7.6 (or the compiler) are somehow more restrictive about environment space, or something like that. Does anyone have any experience with this? -- Larry
