Can Grow Field and Font Size Problem

I have a VB6 App in which I am using Designers to Produce Reports. In the Detail Section of one of the reports I am setting the Font name and Font Size of a number of Fields
dynamically. The majority of these fields are then being shown correctly (i.e) with the correct font.

My problem however is that I have one Field which has the 'Can Grow' property set to true and this field ignores any changes to the Size of the Font. Unfortunately this field has to be able to grow otherwise the report will not work.

Can anybody provide me with a work around for this problem please ?
Who is Participating?
I was looking for another topic and came across this article from CR.

good luck
What code are you using to produce/print the report?

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

SimonWillisAuthor Commented:
I am using Crystal Reports V8, however the last article that you included sounds very much like the problem I am getting.

In the detail section of the report I reference the fields font property directly. ie.


this really is the crux of the problem. when I change the can grow option to false then the font size does change, otherwise nothing happens.
I'm not sure if this is the case with Crystal Reports, though I've used the Excel Automation objects with VB to format cells, and found that sometimes the order of the commands makes a difference.  You might try the Font Size change before and after the other command.

Good Luck.
SimonWillisAuthor Commented:
Thanks for the info, I have used the runtime library a couple of times for proof of concept but I didn't really want to go down tha route due to the licensing restrictions.

I tried stripping everything out of the except the font statements and I still get the problem i.e.

Private Sub Section3_Format(ByVal pFormattingInfo As Object)
' Detail Section
fldName.Font.Size = 14

End Sub

but the problem still occurrs when cangrow is set.

It may be that this is a known bug in Crystal reports 8 as well as CR.NET. If so then I may have to chat with crystal decisions about some kind of workaround.
SimonWillisAuthor Commented:
Thanks, I have about as much info as I could get now. Cheers !
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.