[AccessD] Printing to PDF on 64 Bit

I wouldn't use > 1 million rows as a reason either since Excel has these
limits regardless of 32 bit or 64 bit.

Rows: 1,048,576

Columns: 16,384

On Wed, Jan 21, 2015 at 12:35 PM, Gary Kjos <garykjos at gmail.com> wrote:

> I have no experience with 64 bit Access. My only exposure to it was
> that it was mistakenly installed on my new 64 bit Windows 7 machine at
> work and after I realized it was 64 bit Office I immediately had the
> machine reimaged with a fresh copy of 64 bit Windows and loaded with
> 32 bit Office and things have been working smoothly since.
>
> As Charlotte said, Microsoft themselves recommends you not use 64 bit
> Office unless you absolutely have to have some feature only available
> there such as spreadsheets larger than 1 million rows.
>
> Sorry can't help you with this one. Good luck with it.
>
> GK
>
> On Tue, Jan 20, 2015 at 8:12 PM, David Emerson <newsgrps at dalyn.co.nz>
> wrote:
> > Hi Listers,
> >
> >
> >
> > Access 2010 with SQL Back end.
> >
> >
> >
> > I have a number of reports developed in a 32 bit environment (Access
> 2010)
> > which all work fine when printing to a PDF file.  The record sources are
> > PassThrough queries.
> >
> >
> >
> > I have buttons for printing them to PDF along these lines:
> >
> >
> >
> >         DoCmd.OutputTo acOutputReport, "rptSurvey", "PDFFormat(*.pdf)",
> > strFullName, False, "", , acExportQualityPrint
> >
> >
> >
> > When I run the application on a 64 bit machine with 64 bit Access 2010
> then
> > printing the reports to PDF in most cases causes lack of data on pages
> after
> > the first page and when the report has a subreport Access crashes
> > ("Microsoft Access has stopped working").
> >
> >
> >
> > I can view the reports ok using the following code:
> >
> >
> >
> >         DoCmd.OpenReport "rptSurvey", acViewPreview
> >
> >
> >
> > The problem seems to be with the print to PDF command.
> >
> >
> >
> > I have checked the paths are valid (in the same code I am able to copy
> > spreadsheets to the same folders and carry out automation without any
> > problems).
> >
> >
> >
> > If a report has only one page without any subreport then the PDF is
> created
> > and Access does not crash.
> >
> >
> >
> > If a report has more than 1 page without any subreports then the pdf is
> > created but any pages after the first one have #error where there should
> be
> > data.
> >
> >
> >
> > If a report has only one page including a subreport then the pdf is
> created
> > but Access crashes.
> >
> >
> >
> > If a report has more than 1 page including a subreport on the first page
> > then the pdf is created but any pages after the first one have #error
> where
> > there should be data.  Access crashes.
> >
> >
> >
> > Does anyone have any ideas for me to test?
> >
> >
> >
> > Regards
> >
> > David Emerson
> > Dalyn Software Ltd
> > Wellington, New Zealand
> >
> >
> >
> >
> >
> > --
> > AccessD mailing list
> > AccessD at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/accessd
> > Website: http://www.databaseadvisors.com
>
>
>
> --
> Gary Kjos
> garykjos at gmail.com
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>