Exporting report to HTML "Overflow" error, PDF export works fine

[ramendog]

I need to create HTML export of the report "rpt2024_Tst_summary_8_7_25" in the attached db. The export fails at about page 100 with the "Overflow" error. It is not specific to data in the table at that particular place in the report because I removed the data at the page of the overflow error and the error persisted. It seems to be related to the number of records being generated for the particular "Tst Num" in the report detail section when the error occurs. "Tst Num" with many (hundreds) of records seems to be where the export fails but I don't understand why or how to fix this issue.

The reason I need to utilize the HTML export is to generate web pages with tagging for use in a screen reader.



Any help or leads is greatly appreciated!

Access_test_db.zip

[CJ_London]

Cross posted here

https://www.access-programmers.co.uk.../#post-1971125

for those who don’t want to waste their time offering the same suggestions

[ramendog]

Cross posted here

https://www.access-programmers.co.uk.../#post-1971125

for those who don’t want to waste their time offering the same suggestions

Thank you. I am desperate! (and the forum isn't allowing me to post links to external sites)

[isladogs]

How about saving the report as a PDF. That can be opened in a web browser. Would that work for you?

[ramendog]

Unfortunately, no. PDFs are notoriously bad for screen readers / accessibility and Access doesn’t tag them properly (or at all, doesn’t matter if you check the compliance box on the export output). This is the best solution I’ve found and I need to solve the “Overflow” issue.

[isladogs]

The export fails for me on page 138 also.
The overflow error must be because something is being treated as an integer though I've not managed to work out what or where.

Two things that may be relevant:
1. Neither table has a primary key field
2. There is a lot of repeating data in both tables which appear to be spreadsheets imported from Excel or CSV.
Restructuring to move a lot of repeating data to lookup tables would be more efficient e.g. tblState with fields State & StateName
Similarly fields ABCD_Name, EFG_Name, HJK_Name in the other table / report

Even if they don't solve this issue, they will improve your table structure

I've just posted a link back to this thread at AWF

[CJ_London]

It appears to export successfully to word - which you can then convert to html?

Looks like it is failing on Georgia GA1 where there are more geocodes than will fit on a page - you appear to be only allowing 20 listings per page?

The attached was exported to Word, then saved to html. Not sure if it meets your requirements
rpt2024_Tst_summary_8_7_25.zip

[Welshgasman]

There are 160 records for GA1

How did you limit to 20 per page?

Edit: When I was producing a large pdf file, I broke it down into batches, a-c, d-g etc ?

You could try the same logic perhaps?

[ramendog]

This Word workaround might possibly work, are you using the "Single File Web Page" from the export to generate this file?

Ideally I would resolve this issue in Access as I have script to convert the output that already works. There are reports that output the detail section across more than one page (for example AL7), so I don't think it's the page length per say, but rather something that is happening when the detail section is encountering 100+ records while formatting the report output.

[CJ_London]

are you using the "Single File Web Page" from the export to generate this file?

I tried 2 - both produced the same html so far I could see, but I didn’t do a deep dive into the comparison

[CJ_London]

I suspect that because you have a sub report in the detail section set to can grow, you are exceeding the maximum height allowed for the detail section (22 inches), causing the overflow (the measurement in twips is integer)

[Welshgasman]

This Word workaround might possibly work, are you using the "Single File Web Page" from the export to generate this file?

Ideally I would resolve this issue in Access as I have script to convert the output that already works. There are reports that output the detail section across more than one page (for example AL7), so I don't think it's the page length per say, but rather something that is happening when the detail section is encountering 100+ records while formatting the report output.

The word option does not have links for other pages, so I doubt that would work for you?

[CJ_London]

per post #11 - see my suggestion here:
https://www.access-programmers.co.uk.../#post-1971251

[June7]

I suspect that because you have a sub report in the detail section set to can grow, you are exceeding the maximum height allowed for the detail section (22 inches), causing the overflow (the measurement in twips is integer)

It's my understanding the 22-inch limit is for design view, not printing. A report/subreport that exceeds a page length should just break to another page.

[CJ_London]

Maybe your right, but removing the sub report per the other forum resolved the issue