Tom,
If you can't browse the multi-table view, then the problem isn't with your report, but with the view itself. If your view definition hasn't changed, it's possible there's some kind of data / index / other corruption.
Dawn
-------------- Original message from "Tom Frederick" <[EMAIL PROTECTED]>: --------------
> Larry,
> I can browse the single table view because data shows up. If there is a
> second table, the view is empty. Have not tried the temp table approach.
> The report fails every time the report uses a multi table view. It works
> perfect every time for single. I have gone back to reports I have not
> run in months that use totally different data/views/tables and have
> always worked. They now fail if they are multi table.
>
> All views and reports are built using the Database Explorer menu choices
> like I always have. This only started in the last week or so. Have done
> RELOADS and other suggestions from this group when stuff does not work
> right. Even reloaded V8 because a weird table "484ee4ee" showed up that
> was a duplicate of another table, but I never built it and this was on a
> home machine that no one else messes with. It went away only after I
> erased all rows except the PK row. A puzzler.
>
> 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: Wednesday, July 23, 2008 11:36 AM
> To: RBASE-L Mailing List
> Subject: [RBASE-L] - RE: Reports with no pages.
>
> <<
> I am seeing the same thing.
> >>
>
> Glad to know I'm not going nuts. Well, on this particular matter,
> anyway.
>
> A few questions:
>
> Are the problems you're seeing ONLY in printing reports? Can you browse
> the data in the view? In my experimenting yesterday I found that if I
> tried to count records from the view with a SELECT COUNT before
> printing, I would get back records -- eg, I could "see" them in the
> view. It was only when I went to print the report that I got nothing
> back.
>
> The reports that don't work for you -- do they fail every single time,
> or only sometimes? Mine "start out" okay, but after "some amount" of
> time some of the reports stop working. I'm assuming that I'm doing
> something environmental (too many variables, some setting) that's
> causing it not to work.
>
> You say you've traced the problem to reports based on multi-table views?
> If you PROJECT the data into a temp table and then print, does that
> solve the problem? It would be a work around for me in some cases.
> --
> Larry
>
>
