Re: Nesting Queries, Binding Queries, and Main/Subqueries

[Art DiRamio <ADiRamio@OPENSOLUTIONS.COM>]

While I'm sure the Access reports were written with the best of intentions,
at times it's better to ditch the original structure and work into the
solution from a fresh standpoint.  We run all sorts of different reports
here (bank statements, bills, trials, ad hoc stuff, etc.).  Generally, we
try to get the generic information common for the report in the main SQL,
then get the ancillary data in separate procedures.

  - - Art  :-)


                -----Original Message-----
                From:   David Marut [mailto:David_Marut@ARS.AON.COM]
                Sent:   Wednesday, March 03, 1999 5:12 PM
                To:     Multiple recipients of list SQR-USERS
                Subject:        Nesting Queries, Binding Queries, and
Main/Subqueries

                I am converting a set of reports created in MS Access over
to SQR.  For the
                majority of these reports, the designer has used the
following structure:
                1. query a runs
                2. - query b runs off of query a result set
                3.  - query c runs off of query c result set
                4.   - report uses query c result set

                1. query a runs
                2. query b runs
                3.  - union query joins together the a and b result sets
                4.   - report displays union query result set

                These are both simple examples.  These can extend to 6 or
more levels for
                some reports.  This is easily accomplished in Access because
the queries
                are separate from the report formatting, and Access will
store these all of
                the intermediate result sets until the report is produced.

                My question is - is SQR's Binding Query or Main/Subquery
functionality
                capable of this?  It seems SQR binding ability is really
more like taking
                two distinct queries that have some common element between
them (ie: a
                customer number) and punching out related data on the same
report.

                Manually (using the SQR file), I know I can nest my queries
through sql,
                but I am having an extremely difficult time getting a nested
query to run
                successfully in SQR.  I'm running into variable
naming/referencing issues.

                Any light on these issues is much appreciated.
                thanks,
                David