On Tue, Oct 21, 2008 at 15:38, Cathy Pountney <[EMAIL PROTECTED]> wrote: >> It would be a cursor I generated, so the big detail band would be the >> way to go. Thanks for reminding me that I don't have to put them on >> top of each other, but can Print When... and Suppress Blank Line. > > But ... if you spread them out in the detail band, the report writer will > jump to a new page if the entire height of the detail band doesn't fit on > the page. It doesn't evaluate any of the print when logic before making that > decision. It just assumes the entire detail band needs to print. > > If you end up needing to stack the fields on top of each other, one trick > that is helpful is to lay out the fields for one set, then select them and > mark them as a "Group". Now you can move the entire group out of the way and > start laying out the second set. Lasso those and set them as a "Group". Once > you have all the groups defined, you can lay the few sets on top of each > other. You just have to remember that if you need to edit the report, you > will have to "ungroup" the set of fields you want to edit.
Good stuff to remember, Cathy. Thanks. > Multiple detail bands from VFP 9 could be a solution if you want to go that > route. So, I'd have a single-record controlling alias, and a separate cursor for each section's target alias? That could work... _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
