Hi Drew, > One somewhat more concrete thought, for a report wizard: Grouping on > repeating values. > ... > Think of a simple invoicing system with both an invoice and > invoicedetail table. > A common query for reporting against these tables would be > > SELECT > "Invoices".* , > "InvoiceDetails".* > FROM > "Invoices" INNER JOIN "InvoiceDetails" > ON > "Invoices"."InvoiceID" = "InvoiceDetails"."InvoiceID" > > > Likely then there will be repeating values in the result set for > those columns supplied by the Invoice table. The report wizard could > use this information to determine that a group will be formed for > Invoice. At first glance this would seem to require that the wizard > execute the query and run a pass over the result set. However, much > the same as the form wizard and query designer's Add Table function, > perhaps the report wizard could check for Foreign Key relations and > use these to both determine that a repeating set of values can be > expected, and to determine which column to use for the grouping. In > this case the choice would be "Invoices"."InvoiceID". > ... > The wizard might then ask the user which columns from the Invoice > table to include in the group header. Asking in a subsequent step > which columns to include in the detail section from the > InvoiceDetails table.
hmmm ... I need a one- or two-liner capturing this :) "Report wizard should auto-detect, from the joins of the underlying SQL statement, candidate columns for grouping the report. (Usually: the PK columns participating in a join?)" ? Just to be sure I write down what you mean .... Thanks & Ciao Frank -- - Frank Schönheit, Software Engineer [email protected] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
