Randy:
You put alot of thought into this, and I thank you. You went
exactly the same route that I tried to doing at first. My
problem was in locating each column on the report. Because I
have different indexing levels, and they all have to line up
perfectly, I couldn't think of how to locate each column.
In other words, in a format like this:
4.0 This is a bunch of header text, going onto multiple
lines
5.0 THIS IS A CAPPED HEADING
5.1 This is a bulleted item which might go
into >1 row
5.2 another bullet
You can see that the '5.1' lines up below the text of section
4.0. I can't put the data into separate columns in my table,
because then I'd have to LOCATE separate columns in my report
and they have to line up perfectly. The '5.1' & '5.2' couldn't
be in a separate column, because I would have to locate this
column in the same place that the words following '4.0' would
go! I could put '5.1 blah blah' into one row of data, but if
the text would flow into more than one row, then it would left
justify below the 5.1.
I can't think of how I could use break levels (I was thinking of
assigning each section a separate break value in the table),
because some breaks are bold, some not. And again some breaks
are simple text like 4.0 above, some breaks are one-level indexing,
some are two-level indexing, going into 5.6.1, 5.6.2, etc.!!!!
Mike Young has started me thinking about doing this in HTML and
I'm pretty stoked! Been playing around and aside from some
formatting questions (and page breaks) I think I might be able
to go that route!
Karen
> What if you put each type of data into a different
column based on the type of formatting you want:
ColID INTEGER = RowID for a consecutively numbered row
ColA NOTE = Heading Type A
CoB NOTE = Heading Type B
ColC TEXT = Data of one type such as Underlined Procedure
Names
ColD TEXT = Data of a different type such as bulleted
services
ColE DATE = Dates of scheduled service
ColF NOTE = Chatty informative message
<
