Matt,

Thanks for the information. Glad that one is solved.
It reinforces my belief that 99% of the printing problems
reported in the newsgroups can be cured by updating the
printer drivers. Just wish I had paid attention.<g

Regards,
Jim Cone
San Francisco, USA

wrote in message
oups.com...
Hi Jim,
Problem solved! It wasn't an issue with the spreadsheet after all, but
rather an MS "issue" that I wasn't aware of... I didn't think to search
MSDN before posting here as I should have.
The issue was that because IT was setting up a brand new machine, they
hadn't yet installed any printer drivers before setting up a shortcut
to my workbook and trying to open it... And setting PageSetup elements
without printer drivers installed is a no-no:
http://support.microsoft.com/default...b;en-us;291298
So this issue had absolutely nothing to do with upgrading from Win2000
to WinXP, it was just an "order of operations" thing down in IT and
could just as easily have happened 3 months ago setting up a new
Win2000 machine.
Thanks for your time Jim, much appreciated!
Matt


Jim Cone wrote:
Matt,
You are ahead of me, as you have already tested it
using a string only. So it shouldn't be the userID that is
causing the problem.
As a temporary? crutch, you could put an on error resume next
statement in the code. The printout without a name would
belong to the computer with the problem.
You might want to check if it will work if you put the
code into the Workbook_BeforePrint event.
Also, for what's it worth, I normally use the Excel property...
"Application.UserName" to identify worksheet print outs.
Doubt if I can contribute anything more to this.
Regards,
Jim Cone
San Francisco, USA