Hi,
I wonder if there is anyone out there who has a workaround for a problem I have encountered with Word 2003. This is not quite the same as the problem described by Steve a year ago but is nonetheless a real drag.
After years of resisting making the change I recently upgraded to Office 2003 from Office 2000. Now I find that when I use text boxes or tables in Word on a page that is set up for A4 and using the print layout format, what is shown on the screen is not what prints out. When I print what is supposed to be A4 format I find that what is shown on the layout page is in fact only about ? of the page. As a consequence I wind up not using about a quarter of the page. The only way around this seems to be to take a wild guess at where the real page border are. That is a rather time wasting. hit an miss approach.
This is not satisfactory so I am considering reverting to Office 2000 where what I see on the screen is very close to what comes out on the printer. Has anyone got any ideas on how to get the WYSIWYG in Word 2003 to be truly representational of what is printed before I return to an application that actually does what it purports to do (Office 2000)?
Allen
splowman [at] chanllc.com wrote:
WYSIWYG problem
07-Jan-08
Hello,
I am developing and populating a document using VSTO 2005 and MS Word 2003 SP2
.. Within the document is a table. In the table cells are XML nodes, where
I programmatically populate the XML Nodes in this table. Everything looks
good on screen and in print preview, but when I print the document, part of
the table border is not printing. Also, some of the text from one page will
get pushed down into the next page when its printed. Thus, it is not "what
you see is what you get". The borders of the table are solid line and I have
printed this document to multiple different printers and printer brands (HP,
Xerox, etc.) and I get the same result. However, when I print the document
from Word 2007, everything prints fine. I have about 300 users who are using
this application and the error I have just described is not persistent.
This document was originally created using VSTO and I initially posted to
that group, but when I strip away anything to do with VSTO from the document,
the document not being WYSIWG still persists so I was told to post to this
group from a VSTO MVP
Does anyone know of a solution to this? Is this a known issue with Word
2003? I have a two page document that I could email to anyone who is willing
to help.
Any help would be greatly appreciated.
Steve
Previous Posts In This Thread:
On Monday, January 07, 2008 10:42 AM
splowman [at] chanllc.com wrote:
WYSIWYG problem
Hello,
I am developing and populating a document using VSTO 2005 and MS Word 2003 SP2
.. Within the document is a table. In the table cells are XML nodes, where
I programmatically populate the XML Nodes in this table. Everything looks
good on screen and in print preview, but when I print the document, part of
the table border is not printing. Also, some of the text from one page will
get pushed down into the next page when its printed. Thus, it is not "what
you see is what you get". The borders of the table are solid line and I have
printed this document to multiple different printers and printer brands (HP,
Xerox, etc.) and I get the same result. However, when I print the document
from Word 2007, everything prints fine. I have about 300 users who are using
this application and the error I have just described is not persistent.
This document was originally created using VSTO and I initially posted to
that group, but when I strip away anything to do with VSTO from the document,
the document not being WYSIWG still persists so I was told to post to this
group from a VSTO MVP
Does anyone know of a solution to this? Is this a known issue with Word
2003? I have a two page document that I could email to anyone who is willing
to help.
Any help would be greatly appreciated.
Steve
On Tuesday, January 08, 2008 7:27 AM
Shauna Kelly wrote:
Hi SteveSo you've already ruled out the VSTO solution as the cause of the
Hi Steve
So you've already ruled out the VSTO solution as the cause of the
problem. So let's look at the XML schema. As a diagnostic test, can I
suggest that you try displaying and hiding the pink XML tags (use the
XML Structure task pane - tick the box at the bottom of the pane). Does
one or other make a difference?
And, having hidden the pink XML tags, try showing and hiding the XML
placeholders for empty tags (Tools Templates and Add-ins XML Schema
XML Options).
If that doesn't help, un-hitch the document from the schema and remove
all the pink XML tags. Do you still have the same problem?
If not, then the XML tags are the problem, and I don't know a good
solution. I haven't had great success with the XML tags in tables. Or to
be precise, I've had real troubles with a table within an XML tag. And I
gave up completely on mixing nested tables and XML tags.
If you do still have the problem, then the XML tags aren't the cause.
Are the tables near the edges of the page? Maybe you're running out of
printable area. See:
The bottom of my pages don't print
http://www.word.mvps.org/FAQs/Format...sDontPrint.htm
Or maybe, as I sometimes suspect and can never replicate, there is a
problem with the table style. Try clicking in the table and applying
style Table Normal. Then, add or remove borders as necessary to get the
borders you need. Does that help?
Or, maybe it's a printer driver problem. Make sure that the printer
drivers are up to date and are for the right version of Windows. And,
try printing to a PDF 'driver' such as the free PrimoPDF
(
www.primopdf.com). If it works when printed to the PDF, then you know
it's a hardware printer driver problem.
Hope this helps. If you learn the cause, please let us know in case
others have similar problems in the future.
Cheers
Shauna Kelly. Microsoft MVP.
http://www.shaunakelly.com/word
"Steve565656565656" splowman [at] chanllc.com wrote in message
...
On Tuesday, January 08, 2008 10:43 AM
splowman [at] chanllc.com wrote:
Thank you for your reply Shauna.
Thank you for your reply Shauna.
With respect to the XML nodes, I have already deleted all of the XML nodes,
so the nodes aren't the reason.
I know that the document is not running out of printing area because I can
add a border around the entire page and the border does print.
I have tried three different printers, wheare each printer is a different
brand name. I also saved to Microsoft's xps file type, so i can view it in
internet explorer and the problem still persists there as well.
Currently, the style is normal + Times New Roman and its a requirement to
keep the font in Times New Roman.
I converted the file to PDF using Primo PDF and the conversion is the same
as if it were printed (no WYSIWYG).
Do you have any other suggestions?
Steve P
"Shauna Kelly" wrote:
On Wednesday, January 09, 2008 6:04 AM
Shauna Kelly wrote:
Hi Stevekeep the font in Times New Roman.
Hi Steve
keep the font in Times New Roman.
That sounds like you're talking about the paragraph style(s) used in the
table. What I meant was to change the table style. Select the entire
table (Table Select Table). Using the Styles & Formatting pane,
apply the "Table Normal" style. Adjust borders to suit your needs. Does
that solve the problem? If so, then you could get the TNR font either by
modifying the table style itself, or just adding direct formatting to
the paragraphs as you are doing now.
My only other suggestion would be to try making the borders thicker. If
thick borders work, and thin ones don't, then you'll have an answer,
even if it's not the one you want g.
Hope this helps.
Shauna Kelly. Microsoft MVP.
http://www.shaunakelly.com/word
"Steve565656565656" splowman [at] chanllc.com wrote in message
...
On Wednesday, January 09, 2008 11:49 AM
splowman [at] chanllc.com wrote:
Thank you for your reply.I resolved the issue, or rather a work around.
Thank you for your reply.
I resolved the issue, or rather a work around. There is another one cell
table before the table where I am having problems and the flow for the one
cell table had text flowing around it vs. text not flowing around it. This
property should not make any difference at all for the table I am having a
problem with. Word 2003 should be WYSIWYG and I believe this work-around is
to a bug within Word 2003.
Steve
"Shauna Kelly" wrote:
On Friday, January 11, 2008 8:39 PM
Shauna Kelly wrote:
Hi SteveThanks for posting back with your discovery.
Hi Steve
Thanks for posting back with your discovery. It might help someone else
with the same problems.
Shauna
Shauna Kelly. Microsoft MVP.
http://www.shaunakelly.com/word
Submitted via EggHeadCafe - Software Developer Portal of Choice
Silverlight: Dynamically add "favorites" bookmark link to Page
http://www.eggheadcafe.com/tutorials...namically.aspx