Word vba slow after HP printer install

[David]

I have been using a vba macro in Word 2007 on Vista that normally
completes instantly. It just selects the word to the left of the
cursor, if it is a string of six digits converts it to a spelled out
date, and if it is anything else it inserts a file with the name of
the selected text.

After being provided with a new HP m2727mfp printer/scanner/fax, I
foung that I could not install the software because I am not an
administrator. I had an administrator log on remotely, and I fed the
cd to the computer for the installation. Then he logged off.

I immediately noticed that two of my icons in my quicklaunch toolbar
turned generic, so I changed them. Then I went back to work and found
that my macro took 15 seconds or so to complete. I discovered that
when I printed to my old network printer everything was back to
normal, but if I printed on the HP, the macro was slow again, I was
able to repeat this by switching back and forth, and the slowness
always returned after printing to the HP and always remained until I
printed on the old printer.

In the task manager, the CPU percent was very high in both instances,
but no processes seemed to be hogging the CPU. Any ideas on what the
problem could be?

Thanks,

David

 

[Jonathan West]

You need to get your administrator to come back and do the installation
properly, and to stay until you have conformed that all is well.

It may also be that you need to download a more up-to-date version of the
printer driver from the HP website for whichever version of Windows you are
running.

 

[David]

You need to get your administrator to come back and do the installation
properly, and to stay until you have conformed that all is well.

It may also be that you need to download a more up-to-date version of the
printer driver from the HP website for whichever version of Windows you are
running.

Thanks, Jonathan. I have tried a few things such as disabling the
spooler, but no improvement, so tomorrow the administrator is going to
log back on and we're going to try the installation again, perhaps
with the postscript driver. And I'll make sure that he checks for an
updated driver. I know that with Vista it is generally considered
better for users not to have administrator rights, but when things
like this happen it is a real pain.

Thanks again,
David