On Wed, 21 Feb 2007, Ed Leafe wrote: > Also, with 31 columns, if you add 'group by' statements, you'll have > to group by all the non-derived fields. You might want to limit your > select to only include those fields you care about.
Ed, We -- and others -- care about all the fields. These reports document the input values to the model and may end up supporting a legal challenge to permit issuance. Re-acquainting myself with SQL, I know that I want to use the 'order by' clause in the select statement. I can then use the ReportDesigner() to do the grouping. There are no totals or other aggregates (well, perhaps counts); an orderly record of the inputs is what is needed. Thanks, Rich -- Richard B. Shepard, Ph.D. | The Environmental Permitting Applied Ecosystem Services, Inc. | Accelerator(TM) <http://www.appl-ecosys.com> Voice: 503-667-4517 Fax: 503-667-8863 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
