Office 365 Access, converts an original Access 2000 report (A4 Portait) when converting, in code, to a pdf, using Lebans, only shows a section of A3 landscape. How can this be corrected?

Neil Cliff 0 Reputation points
2026-09-28T16:08:44.77+00:00

For many years, we have happily pdf's using something called Lebans, one and two page reports in Windows 7 and in MSaccess2000, showing Landlords Details, Properties Tenants and rents paid, management deductions and repairs, balance for transfer to bank payment, and an overall accumulating summary throughout a yearly period. It also gathered and attached any copy bills in A4 portrait PDF. which might already exist, The 1st run was a trial sent to myself in Outlook, and if approved, the code written then executed, a second run actually sending by email a copy to the landlord with a full scale report in pdf and any attachments, plus a further back up copy to archive, finally closing off the transaction with a statement date., and removing this property from the current list, before being re constituted for the next month.

Now operating windows 11 and Office 365 Access, the same report resists all formatting changes and the trial round of the statement, cuts off the pdf as though one page of A3 in Landscape, but two thirds of A4 portrait, thus cutting of the summary and VAT section.

I believe I have removed any reference to force new page or anything but A4 portrait with slim borders, yet it always ends up with the short A3 Landscape.

Any guidance would be most helpful as clearly this is a monthly operation for many properties, some with a Landlord with one property, others will multiple properties for which we have written different queries to present the one to many relationship. This has worked now since 1995, and whilst I appreciate we have missed out on updates of windows and Office, is there a section of code which will use "Microsoft to pdf" for example bypassing the only code I am unable to access and place in the section where "print" is the active section or choice?

Yours confused but hopeful

[Moderator note: Personally Identifiable Information removed] 

Microsoft 365 and Office | Access | For business | Other
0 comments

2 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Kai-L 19,920 Reputation points Microsoft External Staff Moderator
    2026-09-28T18:54:58.48+00:00

    Dear Neil,

    That is a long running and clearly business critical process, so losing the bottom of the statement each month is understandably frustrating. Unfortunately, as a forum moderator, I am not able to open your database or run your code to see how the report is being rendered. My role here is limited to general guidance you can apply from your side. From my research, the symptoms strongly suggest that the old Lebans ReportToPDF routine is misreading the report’s page settings under modern Access, rather than the report itself being designed as A3 landscape. Lebans converts an Access Snapshot through older DynaPDF.dll and StrStorage.dll components, and its history includes specific fixes for paper-size, portrait/landscape, and default-printer problems. It was designed for Access 2000-era systems. Access has native PDF output built in, so you can replace the Lebans call with one line.

    1. Swap in the native export. DoCmd.OutputTo acOutputReport, "rptStatement", acFormatPDF, "C:\Statements\Smith.pdf", False. See DoCmd.OutputTo method (Access).
    2. Keep your per landlord filtering. Open the report hidden in preview with your WhereCondition first, then export, then close. OutputTo exports the already open report as filtered, so your one to many queries still work: DoCmd.OpenReport "rptStatement", acViewPreview, , "[LandlordID]=" & lngID, acHidden then the OutputTo line, then DoCmd.Close acReport, "rptStatement", acSaveNo.
    3. Email it directly if you prefer. DoCmd.SendObject acSendReport, "rptStatement", acFormatPDF, sTo, , , sSubject, sBody produces the PDF and attaches it in one step, which suits your trial run to yourself and then the run to the landlord.
    4. Clear the stale page setup. Your report is probably still carrying printer settings saved against a 1990s printer. Open the report in Design view > Page Setup > Page, select Default Printer, then set A4 and Portrait and save. In code this is Reports("rptStatement").UseDefaultPrinter = True, which can only be set in Design view. See Work with form and report printer settings and Set print options in Access.

    One thing worth checking before you start: go to File > Account > About Access and confirm whether you are on 32 bit or 64 bit. If you are on 64 bit, the Lebans DLLs cannot load at all, which on its own explains why nothing you change in the report makes any difference.

    If the native export still crops the page, I recommend that the Global Admin in your organization create a service request with Microsoft Support. A technical support engineer can perform a remote session to investigate the situation, verify the backend configurations, and run any necessary synchronization tools to resolve the problem. If the issue requires further attention, they can escalate it to a specialized team for deeper analysis. For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin. If you don't know who your IT administrator is, please refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support 

    For additional assistance, use this link to find the appropriate contact number from your region: Contact Microsoft customer support | Microsoft Support 

    I hope this information is helpful and provide you with a clear path forward. Should you have any further questions or need additional assistance, please don't hesitate to reach out. I'm always happy to help. Have a wonderful day! 

    If the answer is helpful, please click "Yes" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in the forum documentation to enable e-mail notifications if you want to receive the related email notification for this thread.  

    Was this answer helpful?

  2. George Hepworth 23,120 Reputation points Volunteer Moderator
    2026-09-29T16:49:52.43+00:00

    This problem appears to be very similar to a recent problem in M365 fixed by an update.
    https://www.accessforever.org/post/visual-glitches-and-format-problems

    Compare the version and build of Access you have installed to the builds identified in that article.

    Use the immediate window in VBA to get that information for us:
    ?SysCmd(acSysCmdGetFullVersion)

    Microsoft Access (Version 2609) Build 16.0.20430.20092 Current Channel 32-bit

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.