Roger Lovelock wrote:
>     I am continuing my exploration of dabo - creating a simple CRUD 
> application with both Class Designer and the AppWizard were successful - and 
> while the AppWizard is interesting (and a good code example to dig into) the 
> Class Designer is more my style! 
>    I then went on to explore using py2exe and Inno Setup for application 
> distribution - again a big tick!
>    I am now moving on to look at reporting using the report designer. I've 
> been through Pauls screencasts and all seems pretty straightforward (I have a 
> lot of experience with using Crystal and fyiReportingDesigner).  In Pauls 
> example, of course, the initial .rfxml file is created by the AppWizard and 
> the report is invoked from the menu already created by the AppWizard. I plan 
> to call my report from a button and/or a menu item in a Class Designer 
> created app. I guess to do this I have to manually create an initial .rfxml 
> file to work from and include a test cursor (as I don't want to have to run 
> the AppWizard for every report I want to include in my ClassDesigner app) and 
> also code the action for the button to merge the live cursor and the report 
> definition.
>     Obviously I can dig into the AppWizard code to find out how to do these 
> things - but always wanting to use my time efficiently I was wondering if 
> there are any examples of what I want to do already in existence? If so a 
> pointer in the right direction appreciated.

Just open ReportDesigner, and choose File|New. You'll have an empty report. Now 
if 
you like, follow the example of your AppWizard rfxml to add your test data to 
the xml 
directly (see the xml tab). As soon as you do that, go back to the visual 
screen and 
you should see the test cursor in the object tree.

Paul


_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]

Reply via email to