> The Report Designer seems to work reasonably well but is a bit quirky.
I've
> noticed that when I'm placing RptLabel controls (at the head of report
> columns) that I can't always get underlining to work.

> For example in the Group Header section I place a series of labels:

> Date    Qty    Description    Price    Extended

> Now ... you'd think you can get those to display as underlined by
selecting
> the font and checking the "underlined" property.  Doesn't always work.
When
> I set them at "Arial" - no matter what size I use I simply can't get them
to
> show up underlined on the report.  However if I set the font to "Tahoma" I
> can just set the "underlined" attribute of the first label on the row and
> the entire row shows underlined.  (Huh?)

> Are there some rules regarding how this thing works or is this just a bug?

>> Has anyone else around here used the built-in ActiveX Data Reports in
>> VB6?

>> The Report Designer seems to work reasonably well but is a bit quirky.
> I've
>> noticed that when I'm placing RptLabel controls (at the head of report
>> columns) that I can't always get underlining to work.

>> For example in the Group Header section I place a series of labels:

>> Date    Qty    Description    Price    Extended

>> Now ... you'd think you can get those to display as underlined by
> selecting
>> the font and checking the "underlined" property.  Doesn't always work.
> When
>> I set them at "Arial" - no matter what size I use I simply can't get them
> to
>> show up underlined on the report.  However if I set the font to "Tahoma"
>> I
>> can just set the "underlined" attribute of the first label on the row and
>> the entire row shows underlined.  (Huh?)

>> Are there some rules regarding how this thing works or is this just a
>> bug?

> Yes, the designer can be VERY squirrelly at times. The only rule is don't
> use it if you can use something else. Make that *anything* else. <bg>

> It often helps to perform any 'formatting' in the Initialize event...

> Private   Sub   DataReport_Initialize()  .
> Dim ctrl As Variant
>    ' Group Header := Section6
> For Each ctrl In DataReport1.Sections.Item("Section6").Controls
>    Select Case TypeName(ctrl)
>       Case "RptLabel"
>            With ctrl
>                .Font.Name = "Arial"
>                .Font.Size = 10
>                .Font.Bold = True
>                .Font.Italic = False  ' just for show
>                .Font.Underline = True
>                .FontColor = vbRed
>             End With
>     End Select
> Next

> It is probably just supersition, but I also remove everything but the
> default properties in the designer property setup.

> Odd things still happen, but this does have the advantage of at least
> being
> consistent. <g>

> hth
> -ralph

> Thanks for the ideas!

> The stuff I'm doing with it is pretty simple so I can put up with it.  I
> imagine if I want to do anything more complex I ought to get a copy of
XTAL
> Reports.

> Thanks again.

> -bruce :-)

>> Ralph,

>> Thanks for the ideas!

>> The stuff I'm doing with it is pretty simple so I can put up with it.  I
>> imagine if I want to do anything more complex I ought to get a copy of
> XTAL
>> Reports.

>> Thanks again.

>> -bruce :-)

> There are lots of very good products, for considerably less, that can do a
> wide range of jobs quite well. They are usually easier to program, more
> reliable, with better performance. (I use ActiveReports)

> Personally I find Crystal only useful for Enterprise Solutions; when
> someone
> else is paying for it; and handling all the user training. <g>

> -ralph

>> Active Reports, eh?  Hmm ... OK, I'll check that out.
>> And yes, I agree ... I wouldn't want to pay for a Crystal
>> developer's license either.  The application isn't enterprise
>> level at all - I just need something relatively simple.

> Then you could have a look at the small ReportEngine,
> built into my (Freeware-)Toolset:
> www.datenhaus.de/Downloads/dhRichClientDemo.zip

> This offers you exact placement-capabilities over your
> (Printer-)Page-Drawings (defaults are coordinates in
> Millimeters, but you can change the Coord-System,
> to work with inches too if you want).
> It works at a lower level, since you will have to code
> all your drawings in your own loops, but it has a builtin
> Multipage-Document-Format (based on Windows-EMF),
> supporting a Mix of "normal"- and landscape-pages in
> the same document - and it has a builtin wysiwyg-page-
> preview, showing you the content of that document-
> file-format. Included are examples, how to render e.g.
> Recordset-Contents across multiple pages, supporting
> Header- and Footer-lines, etc...
> In short: you will have to "formulate" your Report in
> small VB6-Subroutines - you will work more close
> to the metal, but with full control over anything on a
> page. The printing-routines finally take the physical
> Printer-Borders into account automatically, so you
> will find your outputs at exact the same mm or inch-
> coords you have given whilst creating/drawing your
> Report-Document.

> Olaf