Tech Support > Microsoft Windows > Home and office > Printer error with Office 2007 in Vista
Printer error with Office 2007 in Vista
Posted by Howard Kaikow on June 29th, 2008


Printer is connected to a router using cable.
No printer is directly connected to the Vista system.
Vista is hooked up wireless.

Both Word and Powerpoint have no trouble using the print.

In Excel, I get the message "Current printer is unavailable".

Note that I can print with Notepad and IE 7.

VB 6 IDE results in "Problem getting printer information from the system.
Make sure the printer is set up correctly".

One issue is the inconsistency within the Office apps.
The other is VB 6.


Posted by Bob Buckland ?:-\) on June 29th, 2008


Hi Howard,

You may want to use the link below to also post in the MS Office Excel discussion group, or you may want to check in the Windows
Vista Print & Fax discussion group. There were similar issues in the scenario you described with Windows XP that required a hotfix
if it was happening outside of Excel, but there was also a method of fixing it, capturing a Printer Port port, if I recall, but it's
been awhile.

I'm assuming that the printer driver is a Vista compatible one.

The Office apps use printers differently for page layout, for example, before you ever print, so yes there is some differences in
how the printer is accessed by each.

===========
<<"Howard Kaikow" <kaikow@standards.com> wrote in message news:uc44YZZ2IHA.2188@TK2MSFTNGP04.phx.gbl...
Printer is connected to a router using cable.
No printer is directly connected to the Vista system.
Vista is hooked up wireless.

Both Word and Powerpoint have no trouble using the print.

In Excel, I get the message "Current printer is unavailable".

Note that I can print with Notepad and IE 7.

VB 6 IDE results in "Problem getting printer information from the system.
Make sure the printer is set up correctly".

One issue is the inconsistency within the Office apps.
The other is VB 6. <<
--
Please let us know if this has helped,

Bob Buckland ?:-)
MS Office System Products MVP

LINKS
A. Specific newsgroup/discussion group mentioned in this message:
news://msnews.microsoft.com/microsoft.public.excel
or via browser:
http://microsoft.com/communities/new...t.public.excel

B. MS Office Community discussion/newsgroups via Web Browser
http://microsoft.com/office/communit...s/default.mspx
or
Microsoft hosted newsgroups via Outlook Express/newsreader
news://msnews.microsoft.com






Posted by Howard Kaikow on June 29th, 2008


"Bob Buckland ?:-)" <75214.226(At Beautiful Downtown)compuserve.com> wrote
in message news:%23AErmLg2IHA.524@TK2MSFTNGP05.phx.gbl...

I'll take a look at your links on the 'morrow.

If I do a Shut Down, Restart and immediately run an Excel maxro that
references the PagesEtup object, code works.

If I them immediately, try the same code from VB 6, does not work.

Then, if I go back to Excel, again, it does not work.
But I can still print from Word, PowerPoint, etc, and Notepad.

Indeed, I just printed from Word and Powerpoint, thjen went back to Excel
and was able to print from Excel.

Now to try the macro again, ..., this time it worked!

So, I am beginning to suspect NIS 2008 as interfering.

Note that I saw a reference to a similar issue for which the cause was a bug
in the AVG auntie-virus program. Somebody said that there was a workaround,
but did not give the workaround.

I'll have to look into this on the 'morrow.



Posted by Howard Kaikow on June 30th, 2008


THis might be the workaround:

http://www.howtonetworking.com/vista/remapprinter.htm


Posted by Howard Kaikow on July 1st, 2008


Bingo!
Eureka!
Whoopee!

I believe that I found a fix!

On the Vista system, I changed the default printer to Microsoft XPS Document
Writer.
Ran the VB 6 program that uses Excel, no problem.
Printed from VBIDE, no problem.
Printed from Excel.no problem.
I then changed the default printer to the Brother HL-2170W.
Voila!
All appears to now work!
At least VB 6 and Excel do!


Posted by Howard Kaikow on July 1st, 2008


"Howard Kaikow" <kaikow@standards.com> wrote in message
news:eNUcDs22IHA.2336@TK2MSFTNGP03.phx.gbl...
Spoke too soon.
It's broken again.




Similar Posts