# Adjust Y Position on Report Detail for Label Printer

**URL:** <https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106>\
**Category:** questions\
**Tags:** report\
**Created:** [May 13, 2026, 8:36pm UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106 "2026-05-13T20:36:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jorge-paladino](https://clarionhub.com/user_avatar/clarionhub.com/jorge-paladino/32/2847_2.png) [@jorge-paladino](https://clarionhub.com/u/jorge-paladino)\
**Post date:** [May 13, 2026, 8:36pm UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/1 "2026-05-13T20:36:13Z")

</div>

Good afternoon!  
I’m trying to edit the Y-position of a report; it’s labels.  
But I can’t find the point to adjust it.  
Can anyone help me?  
I’m trying to use

```clarion
REPORT$?detail_termica{PROP:Ypos}=1

```

or

```clarion
SetTarget(report)
REPORT$?detail_termica{PROP:Ypos}=1
settarget()

```

But the `?detail` tag doesn’t change position.  
I need this because label printers have different values ​​for this starting position.  
I would like to be able to edit this according to the client’s printer.

My report

```clarion
REPORT REPORT('Etiquetas A4'),AT(1,15,41,25),PRE(RPT),PAPER(PAPER:USER,2350,1580),FONT('MS Sans Serif', |
          8,,FONT:regular),MM
detail_termica DETAIL,AT(0,0,43,25),USE(?detail_termica),#ORDINAL(1)
            STRING(@s45),AT(3,0,39,4),USE(Qtq_:Line1),FONT('Tw Cen MT Condensed',10,,,CHARSET:ANSI), |
              TRN,#ORIG(?String1),#ORDINAL(2)
            STRING(@s45),AT(3,4,39),USE(Qtq_:Line2),FONT('Tw Cen MT Condensed',10,,,CHARSET:DEFAULT), |
              TRN,#ORIG(Qtq_:Line1),#ORDINAL(3)
            STRING(@s45),AT(3,8,39),USE(Qtq_:Line3),FONT('Tw Cen MT Condensed',10,,,CHARSET:DEFAULT), |
              TRN,#ORIG(Qtq_:Line1),#ORDINAL(4)
            STRING(@s50),AT(3,14,37,9),USE(Qtq_:Line7),FONT('C39HrP24DhTt',25,,,CHARSET:ANSI), |
              CENTER,#ORIG(Qtq_:Line5),#ORDINAL(5)
          END
        END

```

It is programmed to `y=15`, but in some cases I need to change it to 0, for example.  
I would like to do this with variables, without having to modify the report.

Thank you!

---

<div class="post-metadata">

**Author:** ![jslarve](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/e480ec/32.png) [@jslarve](https://clarionhub.com/u/jslarve)\
**Post date:** [May 13, 2026, 9:07pm UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/2 "2026-05-13T21:07:14Z")

</div>

You can’t really fight the report by changing the detail’s position like that (unless you want to use ABSOLUTE and own the position every time 🙂 )

I would query the printer’s printable area, then set the report’s dimensions. Then the detail will print where it’s supposed to go, naturally.

---

<div class="post-metadata">

**Author:** ![PurpleEdge2214](https://clarionhub.com/user_avatar/clarionhub.com/purpleedge2214/32/5109_2.png) [@PurpleEdge2214](https://clarionhub.com/u/PurpleEdge2214)\
**Post date:** [May 14, 2026, 2:14am UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/3 "2026-05-14T02:14:44Z")

</div>

Try adding a report header and adjusting the height of that.

A detail prints at wherever the report print head is at the time, automatically, so I don’t think you can change it?

---

<div class="post-metadata">

**Author:** ![CarlBarnes](https://clarionhub.com/user_avatar/clarionhub.com/carlbarnes/32/1859_2.png) [@CarlBarnes](https://clarionhub.com/u/CarlBarnes)\
**Post date:** [May 14, 2026, 2:03pm UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/5 "2026-05-14T14:03:41Z")

</div>

> [@jorge-paladino](#):
>
> ```auto
> REPORT REPORT('Etiquetas A4'),AT(1,15,41,25),PRE(RPT),PAPER(PAPER:USER,2350,1580),FONT('MS Sans Serif',8,,FONT:regular),MM
> detail_termica DETAIL,AT(0,0,43,25),USE(?detail_termica),#ORDINAL(1)
> 
> ```

You need to adjust the Report `AT(1,15,41,25)`.

That Report AT() is what defines the X/Y and Width/Weight of the “Print Area” for Details, so that lets you adjust the position of all details on a page. You probably have just 1 detail, but it works the same.

In Designer you would find this on the “Report Designer” menu an item named “Page Layout View”. Normally you work in “Band View”.

* * *

Since you just have 1 Detail an alternative would be to add the “ABSOLUTE” attribute to the DETAIL. Then the Detail AT(X,Y) is relative to the Page not the Report so `REPORT$?detail_termica{PROP:Ypos}=1` would work to move it up to 1. IIRC ABSOLUTE only allows one detail per report page.

---

<div class="post-metadata">

**Author:** ![jorge-paladino](https://clarionhub.com/user_avatar/clarionhub.com/jorge-paladino/32/2847_2.png) [@jorge-paladino](https://clarionhub.com/u/jorge-paladino)\
**Post date:** [September 14, 2026, 12:00am UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/6 "2026-09-14T00:00:21Z")

</div>

I didn’t solve it; I created new reports—one for each label type… unfortunately.  
Thanks.

---

<div class="post-metadata">

**Author:** ![Julian](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/74df32/32.png) [@Julian](https://clarionhub.com/u/Julian)\
**Post date:** [September 15, 2026, 5:48am UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/7 "2026-09-15T05:48:56Z")

</div>

I note your workaround but this is what I did .. [Printing Avery Labels - 65 per page](https://clarionhub.com/t/printing-avery-labels-65-per-page/7689)

---

<div class="post-metadata">

**Author:** ![Jane](https://clarionhub.com/letter_avatar_proxy/v4/letter/j/ecb155/32.png) [@Jane](https://clarionhub.com/u/Jane)\
**Post date:** [September 15, 2026, 7:15pm UTC](https://clarionhub.com/t/adjust-y-position-on-report-detail-for-label-printer/9106/8 "2026-09-15T19:15:29Z")

</div>

You might also get some ideas from Lee White’s [“nudge” code](https://clarionmag.jira.com/wiki/download/attachments/399458/cmag-2000-10.pdf?api=v2) as published in Clarion Mag long ago (page 45 in the PDF).

You can also find his zip of sample code in the cmag repository.
