Just when you thought it was safe... So the client loved the proofs I came up with from the last edits. That got them thinking though, and now they have some new ideas.
The way the tables were set, I was placing the <Origin> field in the black bar, then listing all of California. When Origin changed, a new page began and the next set began (Oregon, etc.). The client would like to have no page breaks between Origins, so when California ends, the Oregon bar appears and that list starts.
I've played around with this a couple of ways; to my slow mind, I don't see a good way to do that with the Origin bar in a separate box. I can place it as an inline graphic in the text box, but I was thinking about a repeatable component. I have created that template and placed it in a new rule ProductTable2; the Origin bar appears but the table doesn't start composing after.
Finally, they would like the producer (winery, distillery, etc.) appearing as a new column - but only when it changes, so it acts as a divider. The logical way to do this seems to be defining the data file by Producer instead of Origin - but this creates a potential issue with the Origin bar solution.
So I guess I have several questions -
1) How would you suggest running this solution so there are not page breaks between Origins?
2) Can I define by two variables in a multi-line record to utilize the Origin bar but also use the Producer as a variable?
3) Can I put the repeating component in the same box with a table?
4) Most importantly, when will I learn to say no to clients?
Thanks for your advice and expertise. I'm seeing what they want to achieve, but struggling to picture how to create it. WWinsidepageREPEATABLE8-15.zip