Re: Report
- From: erewhon@xxxxxxxxxx (J French)
- Date: Tue, 16 May 2006 07:23:33 GMT
On Mon, 15 May 2006 21:15:47 GMT, "Ivar"
<ivar.ekstromer000@xxxxxxxxxxxx> wrote:
"will be a doddle, a virtual "one liner"."
A ONE LINER!!!!! I'm half way through doing a similar thing, and I'm up to
160 lines already, and that's without the report header and footer, or the
page headers and footers.
But then again, I am working with classes and collections rather than a
recordset, with a lot more fields, and generating a print preview, and
formatting and aligning each field, while calculating page breaks and
dealing with single and multiline fields. And calculating totals and sub
totals along the way, and changing the colours of the text depending on the
fields values and I dare say some other stuff that has been lost in the code
somewhere.
Ivar, it is a profoundly good idea to separate the printing and
calculation
Ideally wrapping the actual printing in a Class that 'prints' onto an
Object that might be a Printer or a Picturebox
You'll find that the control code becomes much simpler, and the Print
Class is re-useable so it becomes stable and fully featured.
Some time ago I wrote something called gPrint.cls
( Google Groups : vb gprint "J French" )
That might give you some ideas
Normally I use a text file containing a Template and simply ram the
data into the fields which makes simple report printing very easy.
.
- References:
- Report
- From: a2d2
- Re: Report
- From: Mike Williams
- Re: Report
- From: Ivar
- Report
- Prev by Date: Re: ActiveX control with asyncronous notifications
- Next by Date: Re: Reinstall VB6
- Previous by thread: Re: Report
- Next by thread: Re: Report
- Index(es):
Relevant Pages
|
