G
GS
After serious thinking Clif McIrvin wrote :
Thanks Clif! I didn't know about this property and so will investigate
it more. I've always suspected, though, that PageSetup processing
differed for different printers. During this exercise I was wondering
if setting ActivePrinter="" would be helpful b ut haven't gotten around
to checking it out.
Regardless, McGimpsey's rework of John Green's XL4M solution works
really well and so I'd rather run with that than mess around with
hardware or hardware settings in a 'workaround' fashion when a simple
solution exists already.<g>
<...>
I just today stumbled across this new-to-2010 property:
Application.PrintCommunication Property
Specifies whether communication with the printer is turned on. Boolean
Read/write
Version Added: Excel 2010
Set the PrintCommunication property to False to speed up the execution of
code that sets PageSetup properties. Set the PrintCommunication property to
True after setting properties to commit all cached PageSetup commands.
---
I don't recall if the Excel version was mentioned in this thread ... curious
if PrintCommunication=False makes any noticeable difference in the PageSetup
versions of the macros or not.
Thanks Clif! I didn't know about this property and so will investigate
it more. I've always suspected, though, that PageSetup processing
differed for different printers. During this exercise I was wondering
if setting ActivePrinter="" would be helpful b ut haven't gotten around
to checking it out.
Regardless, McGimpsey's rework of John Green's XL4M solution works
really well and so I'd rather run with that than mess around with
hardware or hardware settings in a 'workaround' fashion when a simple
solution exists already.<g>