Report Access Convert to PDF

Report Access Convert to PDF

Introduction PDF

PDFs run your world. You know you use PDFs to make your most important work happen. That's why we invented the Portable Document Format (better known by the abbreviation PDF), to present and exchange documents reliably — independent of software, hardware, or operating system.

The PDF is now an open standard, maintained by the International Organization for Standardization (ISO). PDF documents can contain links and buttons, form fields, audio, video, and business logic. They can be signed electronically, and you can easily view PDF files on Windows or Mac OS using the free Acrobat Reader DC software.

Introduction Report Access

Reports are a great way to organize and present data from your Access database. Reports enable you to format your data in an attractive and informative layout for printing or viewing on screen. Reports are often used to present a big-picture overview, highlighting main facts and trends.

here is one aspect of using this very convenient method that I frequently see people struggle with. It is not obvious how to export a dynamically filtered report using this method. Other than the DoCmd.OpenReport-Method, the DoCmd.OutputTo-Method does not support supplying any criteria to the report the filter the data. Therefore, it seems to be a problem to export a report that displays different data sets depending on user input or other factors.

The obvious workarounds that come to mind are usually one of the following:

    Create different reports with the criteria built-in

    Create a parameter query referencing form fields or global functions as a record source for the report.

    Build the SQL for the report at runtime and assign it to the report.

All of these do work. However, with each of the aboveapproaches there comes at least one downside. (Matching theabove order):

    It requires creating multiple very similar objects (reports). - Not very flexible and a maintenance burden.

    It requires additional functions or a form and is rather inflexible.

    It requires building the whole query at runtime and assign it to the report in its Report_Open-Event. - Valid approach, but somewhat complex, error-prone, and messy due to the dependence on an external (to the report) source for the SQL string.

Example

Private Sub cmdReporttoPDF_Click()
Report="UserLogin2
Path="D:\123\1\"
docmd.OutputTo acOutputReport, Report, acformatPDF, Path & Replace(CurrentProject.Name, ".accdb", ".pdf"),false
End Sub

Please Watching My Video is Below

Design by Vannak Vannaro