September 15, 2009 at 12:45 am
As far as I know font is set per element.
If you know you are only going to use one font (as we do) then store it in a field named something like 'GlobalFont' and apply GlobalFont to each element it is required upon. I'd suggest FontSize will be different for different types of elemnt on your report, e.g. 'TableHeaderFontSize' 10, 'ReportHeaderTitleFontSize' 16. You have to make a decision as to what is useful to be databased and that will be elements that are regularly the same between your reports. I have found that storing about 20-30 properties + 20-30 other metadata items gives me an optimal advantage.
M
SQL Novice - Here to learn.
September 15, 2009 at 6:27 am
Sorry about the LOOOONNNG delay in replying to your question. I was pulled off to another project and just now am getting back to this one.
Maybe this will help. Most reports are like:
HEADER HEADER HEADER
Result Result Result
I want my report to come out looking like
HEADER Result
HEADER Result
HEADER Result
Does that make more sense?
September 15, 2009 at 6:50 am
Yes - i understand now.
If you wish to display your data in a table, then transpose your results (within your SQL Stored Procedure/Query) and send through the required 'header' as the first record for each row.
e.g.
Field1 Field2 Field3 Field4
HEADER DATA1 DATA2 DATA3
Make sense?
Its also possible you could use a matrix to good effect, although I tend to find their display flexibility reduces their display capability when it comes to formatting.
M
SQL Novice - Here to learn.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply