Possibly a bug in the way linked queries are parsed.
Hi,
We have a setup with RB Ent 7.02, DOA against Oracle, and our end user
create reports.
One of my end user set up a report like this:
- A Query, not used in any report/subreport. This Query was only there to
provide a central Autosearch for the user.
The search is a a date range, plus a site selection because this was
suppopsed to be a per site report.
This setup was to avoid the user having to input the same date-range and
Site information 6 times.
- 6 sub-queries linked to the "main Query" on same table, and on primary key
These sub-queries have their own search set (not Autosearch).
In one of the sub-set's searches there was an OR statement.
This caused the sub-set to produce records that wasn't restricted to
criteria of the "Main Query" that it was linked to, if you see what I mean.
So it seems the part of the where statement that was added from the Link was
inserted as part of the OR statement.
When I added "parantheses" around the OR expression of the subset, it
worked.
If you want detailed information with actual tablenames, and how it's set
up, just ask.
Best Regards,
Paul Wiik
We have a setup with RB Ent 7.02, DOA against Oracle, and our end user
create reports.
One of my end user set up a report like this:
- A Query, not used in any report/subreport. This Query was only there to
provide a central Autosearch for the user.
The search is a a date range, plus a site selection because this was
suppopsed to be a per site report.
This setup was to avoid the user having to input the same date-range and
Site information 6 times.
- 6 sub-queries linked to the "main Query" on same table, and on primary key
These sub-queries have their own search set (not Autosearch).
In one of the sub-set's searches there was an OR statement.
This caused the sub-set to produce records that wasn't restricted to
criteria of the "Main Query" that it was linked to, if you see what I mean.
So it seems the part of the where statement that was added from the Link was
inserted as part of the OR statement.
When I added "parantheses" around the OR expression of the subset, it
worked.
If you want detailed information with actual tablenames, and how it's set
up, just ask.
Best Regards,
Paul Wiik
This discussion has been closed.
Comments
in order to have the OR condition be applicable because everything else is
implicitly AND'ed together. Can you reproduce a scenario in DBDemos that
shows the problem if you feel it is a bug? We can research it here to see if
there is a modifcation we can make to the SQL generation logic. Send all
attachments to support@digital-metaphors.com
Cheers,
Jim Bennett
Digital Metaphors
http://www.digital-metaphors.com
info@digital-metaphors.com