Thanks - appreciate the comments - I will give it a bit more thought before
I proceed. I like the idea of report classes as you describe - just don't
need the extra form and button to click.
Rodgy
----- Original Message -----
From: "Paul McNett" <[email protected]>
To: "Dabo Users list" <[email protected]>
Sent: Saturday, December 13, 2008 4:39 PM
Subject: Re: [dabo-users] Fw: Running a Report
> Roger Lovelock wrote:
>> I have been thinking about my question below and my gut feeling is that I
>> should combine the two FrmReportxx routines, get rid of the little form
>> with its OK button and make the whole thing a form method (and obviously
>> change my call from the button acordingly). Comments?
>
> I think you should do what feels right to you. There's no one-true-way.
> The reason I
> made FrmReportBase and FrmReportSample was to give you code to pull from.
> It does
> make some sense to have a base class with the common report functionality
> that you
> want to use in your app, and to give each report its own subclass so it
> can do
> specific processing/preparation for running a given report, but again it
> is all up to
> you, the application developer!
>
> Paul
>
>
[excessive quoting removed by server]
_______________________________________________
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/4e37856571434f75a8f1b0d8cae8a...@roger
