How get rid of heading on blank page in Report

English
,
#1

I have a LibreOffice report driven off of a database query. The page height is 11 inches. The top margin is .5 inches and the bottom margin is .3 inches, leaving 10.2 inches. There is no footer. The page header is .76 inches in height, leaving 9.44 inches for detail. Each detail section is .58 inches in height. 16 detail lines should total .58 x 16 = 9.28 inches, well under the 9.44 available. Other Detail properties are Force new page None, Keep Together Yes, Visible Yes, Background Transparent Yes, and no Conditional Print Expression.

When I generate a report with 16 detail lines the detail lines all appear on the first page as they should, but Writer generates an additional page with a header and nothing else.

How do I make Writer not create that extra page?

I might add that I would love to make the detail sections a little less high but they are crammed full of all of the information that the client wants in there. There is no easy way to make them less high – and they do fit on the page now. The only problem is the spurious header.

Thanks,
Charles

#2

Have you an empty record in the database?

If not, how did you encode “next record” request? For better diagnostic, attach the report template (from Base component, unless everything is generated from Writer with mail merge, which is not clear from your question).

Don’t forget to mention OS name and LO version.

#3

Have you an empty record in the database?

The report is based on a query. The query returns no blank records.

how did you encode “next record” request?

I am sorry. I am not a LibreOffice expert. I inherited this project. I don’t know the answer.

For better diagnostic, attach the report template (from Base component, unless everything is generated from Writer with mail merge, which is not clear from your question).

Sorry, again don’t know how to do that. No mail merge is involved. The report is based on a database query. I have forgotten how to see that specification. When I click Edit on the Report I go into the Report Designer. How do I see the specification for the input to the report?

Don’t forget to mention OS name and LO version.

That I can do! Windows 11 Pro and LO 24.8.5.2 .

Is it worth mentioning that there are no blank rows printed in the report, neither in this situation nor in the non-problem situation. If the query returns 1 to 15 records all is well. I have not tested 17, but 16 is a problem of a blank page with only a header.

Charles

#4

This means your project is based or uses a document with extension .odb. I seem to remember that W$ hides file extension by default in the file browser. Enable extension display and look for a document ending with .odb. This document contains query definition and report configuration. Attach it here.

To attach a document, click on the seventh icon from left in the comment toolbar. It looks like a desk “out basket” with an up-arrow.

#5

You are asking me to post the entire database in a public forum? That is utterly out of the question. The data is protected by privacy laws and common decency. I am astounded that you would ask.

#6

I am not asking for the DB, of course. I am only asking for the report configuration. This is a very small document with file extension .odb. Its size might be in the 20k-50k range. In your issue, three separate “files” are involved: the DB (may be a MySQL, PostgreSQL, SQLite, a spreadsheet or CSV file), the report generator configuration and the Writer document. The report generator uses data from the DB to generate the Writer document.

The extra page is probably caused by a spurious delimiter/triggering directive (even if the report is built graphically). I offer to have a look at the report structure, independently from any data.

#7

It’s an embedded database, HSQLDB. It’s all one file of 257K.
------ 3/26/2025 12:48 PM 262224 MOW.odb

Here’s the report definition. What should I look for?

image
image1109Ă—538 57.4 KB

#8

A screenshot is insufficient to diagnose the issue. Make a copy of your .odb. Remove data and create two dummy records. Attach the resulting file.

CAVEAT: though you say it is an embedded DB, make sure the .odb does not reference “external storage” to avoid losing real data (I don’t use HSQLDB).

#9

Sounds very much like

tdf#100477

#10

EXACTLY! Thank you.

An oldie but goodie.

What is my next step?

#11

Describe your symptoms on that bug report, and add a sample ODB which allows the behaviour to be reproduced, otherwise the report will likely be closed again.

#12

I opened each report in every bug attachment and did not see any blank pages.

#13

Which is why it was closed as wfm, until I reopened it. Something in the page layout of Writer when the reportbuilder executes causes the extra page to added. Whether this was linked to page size or some other internal mapping problem remained undetermined. Even in the bug report, some testers were never able to reproduce, or only in certain discrete versions, but not in others.

1 Like
#14

There is already a sample in the bug report.

I am not an expert in LibreOffice. Getting my actual tasks done is enough of a challenge. It would be a “project” for me to create a database, create the records, create the report and test it – and even then it might not demonstrate the bug – and even if it did LO might decline to fix it. There is a limit to how much labor I am willing to undertake to fix your bugs. I apologize if that makes me a bad guy. The workaround is to simply not print the extra page.

#15

There are 3 samples with 6 reports. None of them shows the issue on my machine. It is impossible to fix ghost issues.
Make a copy of your database to be uploaded.
From that copy, remove all forms and reports unrelated to your issue.
Delete all table rows except for a few ones as long as the report still shows the issue.
Upload your sample to this place or to the issue.

Impressum (Legal Info) | Datenschutzerklärung (Privacy Policy)   Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.