View Single Post
  #35   Report Post  
Posted to microsoft.public.excel.programming
Robert Baer Robert Baer is offline
external usenet poster
 
Posts: 93
Default Excel print object?

Living the Dream wrote:
Hi Paul

Just putting it out there, and not even sure this is even relevant here for your issue, but! I ran across this when using code to print charts; coding would only print the charts and not the labels or data series. Apparently Microsoft screwed up on one of their Security Patches KB2596596: https://support.microsoft.com/en-us/...cember-13-2011
https://answers.microsoft.com/en-us/...3-5323489abae9

It would seem nobody within my company had ever used coding for specific printing, hence the reason it was never identified until now.

There was a patch to fix this issue:
http://www.microsoft.com/downloads/d...2-d778db920826

Maybe chat with your IT Dept and see if this is an active issue within your version of office.

The paranoid control freaks in my IT Dept are refusing to apply the fix for little ol' me, because it has global implications for the entire network, blah, blah, go figure!

HTH
Cheers
Mark.


Me, myself and I constitute "our" IT Dept.
All of us have various versions:
Microsoft Office 2000 Premium (4 disc set)
" " Student and Teacher Edition 2003
" " Student and Teacher Edition 2007
" " Student and Teacher Edition 2010

And as everybody EXCEPT Microsoft knows, the "help" is jusssst enough
to "justify" the label but no more than that.
Never any real-world WORKING examples, just generic useless pablum,
if any at all.
"On Line" is not much better.

NO useful ideas to automate printing of an object to a <path/<file
name supplied by program.file type fixed by programmer.
Everyone and their pet goldfish wants to print cells - which are
BEHIND the object.

Found that if i cheat like hell by Set Print Area to cells in same
place as object, that if i manually then print to manually set
path/filename.filetype, i get reasonably close to what i visibly want.
Note that is not printing the cells per se, just whatever happens to
be in that area.
And then go back to the program, continue it to reset the various
objects and variables to starting state.

At one time, ages ago, the following worked":

ActivePrinter = "Acrobat PDFWriter on FILE:", PrintToFile:= True, _
ActiveWindow.SelectedSheets.PrintOut Copies:=1, Preview:=False, _
Collate:=False, PrToFilename:=pPath + vNam + ".PDF"

....and that was incrementally derived by "hints", similar to what Excel
gives on function equations for a cell.