Jim Dettman
jimdettman at verizon.net
Thu Jan 22 07:02:45 CST 2015
But that's true for any language really, or you need to maintain two separate releases. Nothing in VBA is really the cause of that. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Mark Simms Sent: Wednesday, January 21, 2015 03:49 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] Printing to PDF on 64 Bit This one case so perfectly depicts why it's so brutally difficult to create solutions using Access or any Microsoft Office component that is VBA-driven: You've GOT to use compiler directives to effectively handle all of the variances and exceptions for the various releases. #IF ACCESS2013 Then #ELSE #END IF > > DoCmd.OpenReport "rptSurvey", acPreview, , , acHidden > DoCmd.OutputTo acOutputReport, "rptSurvey", "PDFFormat(*.pdf)", > strFullName, False, "", , acExportQualityPrint > DoCmd.Close acReport, "rptSurvey", acSaveNo > -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com