AdjustObjectSize<\/a> feature for stretching images and shapes.\n<\/p>\n\nAs you probably know, in the ReportListener.AdjustObjectSize event you can consult the MaxHeightAvailable member of the properties object to see how much usable space there is on the rest of the page. By "usable" I mean that this value does not include space in the remaining page length that must be substracted\/reserved for footer elements. (I'm not going to repeat the docs information here, because it's expressed properly there already; this post does not constitute any sort of correction.)\n<\/p>\n
\nThis feature effectively gives us a chance to decide what to do when you want to render dynamic content that is not going to fit on the page. Just as I could write some limited VB code to do what I thought the RS engine might do, you have the ability to make pretty much the same calculation — with whatever rules suit you, in Xbase code — that report engines all have to make in this situation internally, and that report engines often hide from you with almost-as-often annoying results.\n<\/p>\n
With great power comes great responsibility<\/h4>\n
\n
\nRemember: The RS engine chooses what to do to avoid a possible infinite push-down loop. Its choice is as follows: push down once if an item does not fit. Then, on the next page, if the item still<\/em> won't fit even though it has the full usable page to deal with, unilaterally choose a pagination method for the item's content to break it up between pages.\n<\/p>\n\nIn VFP, it's up to you. You get MaxHeightAvailable to help you make your decision about what Height should be used. You can set it too high for the remaining page space, forcing a page break if you want.\n<\/p>\n
\nAlternatively, if you set Height lower, you can make the thing fit on the current page. You can then use the Reattempt member value of the properties object, on the next page, to decide what you want to do there. If you do not pay attention to Reattempt, and again set Height to a value that still won't fit, you can in fact cause an infinite push-down loop to occur.\n<\/p>\n
\nWhen you think about what you might do with this capability, remember that the shape or image layout element might just be a placeholder for other custom content (RTF, anyone?) that you are shoehorning into this report.\n<\/p>\n
\nRather than post an example here, I'm going to ask you to check the code that gets generated for an image or rectangle when you set Dynamic conditions for its Height or Width in SP2. <\/p>\n
Press the Script<\/strong>… button from the Dynamics<\/strong> tab in the ReportBuilder Properties dialog, and don't forget that you can Code Zoom<\/strong> from there for a closer look. You may have to change your preferences for .TXT files to get syntax coloring in the Code Zoom dialog.<\/p>\nIt's worthwhile getting used to doing this, and besides, you'll see that the code there observes other niceties, such as the overall max allowable values, which you'll also find listed in FOXPRO_REPORTING.H: <\/p>\n
#DEFINE <\/font>FRX_RUNTIME_LAYOUT_DIMENSION_LIMIT 64000<\/font><\/p>\nThere's also helpful information in editboxes within the ReportBuilder dialogs.\n<\/p>\n
\nAnd there you have it.\n<\/p>\n
You can hunt your own game and bring it to the table, or you can shoot yourself in the foot. <\/h5>\n
\n
\nIsn't that, yea verily, the essence of the VFP way?<\/p>\n","protected":false},"excerpt":{"rendered":"
This one is for you VFP reporting folks, although the subject comes to mind by way of a SQL Server reporting conundrum in the forums recently. The problem-to-solve is one of those Reporting Convergence things you'll see no matter where, and how, you report: How do you handle stretching content that is longer than a singleRead more<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,9],"tags":[],"class_list":["post-173","post","type-post","status-publish","format-standard","hentry","category-reporting","category-visual-foxpro"],"_links":{"self":[{"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/posts\/173","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/comments?post=173"}],"version-history":[{"count":0,"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/posts\/173\/revisions"}],"wp:attachment":[{"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/media?parent=173"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/categories?post=173"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/spacefold.com\/lisa\/wp-json\/wp\/v2\/tags?post=173"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}