Report record field $vertextend

[Nick Renders]

Hi Rudolph,

The Totals section has a from-bottom-margin specified, because I want it always printed at the bottom of the (last) page.
But you are correct: adding a Positioning section below the field will solve my problem. Thanks for the tip!

On a related note: the Record section has a $userecspacing property which is set to kTrue. Any idea what that is supposed to do? The tooltip and Omnis Help don't really explain it.

Cheers,

Nick Renders


On 21 Mar 2025, at 14:42, Rudolf Bargholz wrote:

> Hi Nick,
>
> And normally it makes sense to set $nolineifempty to kTrue (if value empty, the current line will not be printed), and/or $nosecifempty to kTrue (if value empty, the current positioning section will not be printed) in a field with $vertextend set to kTrue.
>
> Your $vertextend field thus only needs to be one line in height. Remember to place a positioning section directly **BELOW** the previous one line vert-extend field.
>
> Regards
>
> Rudolf Bargholz
>
> -----Ursprüngliche Nachricht-----
> Von: omnisdev-en <omnisdev-en-bounces at lists.omnis-dev.com> Im Auftrag von Rudolf Bargholz
> Gesendet: Freitag, 21. März 2025 14:33
> An: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
> Betreff: AW: Report record field $vertextend
>
> Hi Nick,
>
> I think you are overthinking this. Omnis will start printing the subtotal or total only after the vertically extended text has been printed. There is generally no need to do any complex counting, unless you try some complicated stuff with the report. The reports flows, from record to record, and from section to section, printing the previous section before you print the next section. Unless you specify a from-top-margin, from-bottom-margin, from-top-of-previous-section or something similar, text overwriting other text almost never happens.
>
> As a general rule, to prevent overwriting of text, place a positioning section directly **BELOW** the previous vert-extend field, and you are fine.
>
> Regards
>
> Rudolf Bargholz
>
> -----Ursprüngliche Nachricht-----
> Von: omnisdev-en <omnisdev-en-bounces at lists.omnis-dev.com> Im Auftrag von Nick Renders via omnisdev-en
> Gesendet: Freitag, 21. März 2025 14:16
> An: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>
> Cc: Nick Renders <omnis1 at arcict.com>
> Betreff: Report record field $vertextend
>
> Hi,
>
> This might be a no-brainer, but after all this time, Omnis Reports are still a dark art like alchemy to me. So I am asking the almighty Omnis List before I inadvertently summon Beelzebub.
>
> I have a simple Report class: Header - Record - Subtotals - Totals sections.
> In the Record section, there is a Field that can have lots of text, or only a few words, depending on the Record.
> This Field has its $vertextend Property set to kTrue, so some records are only one or two lines, while others can be 10 or more lines long.
>
> The Record section will start a new page if less than 6 cms are available (metric system, not sure if that is a pro or con when performing alchemy). As you can guess, this means that the final Record can bleed into the Subtotals and Totals sections if there is lots of text.
>
> So, how do I predict how much space is needed before printing the Record? Counting the characters seems a haphazard solution, considering Fonts, carriage returns/line feeds, etc.
>
> Any ideas?
>
> Best regards,
>
> Nick Renders
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com


Nick Renders

ARC - your ICT service partner
H. D. Saviolaan 8
1700 Dilbeek
T: (00 32) (0)2 466 50 00
F: (00 32) (0)2 466 88 33
http://www.arcict.com