On Fri, 2 Mar 2007, Ed Leafe wrote: > Nah, it's not that bad. Once you're familiar with the rules, it > isn't difficult to make it work.
Where I got totally tangled was with two concepts: 1) that a cursor represents a single and complete 'view' retrieved from one or multiple tables (which is the usual idea of a database cursor), so it needs to be generated by code for each record to be printed ... I think; and 2) that the format of the cursor in the application code (as input data) is not the xml-formatted version require by the template (the .rfxml file) used to format the input for the reportLab engine. 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
