MS Word Formatting

April 1, 2010 at 07:52:16
Specs: Windows 2000
On a recent document when I hide the returns, the document does not recognize section breaks or disregards them and allows text to flow is if no section break had been added. I can resolve the issue in some situations by simply adding returns and removing the section break.

However, in one spot I want to change the formatting of the next several pages from portrait to landscape. When I hide the section break, the first page of the new section reformatted to landscape remains as portrait. I've checked the page setup dialog box to see if the different first page option was checked and it was not.

So, I do not understand why the page formatting would change when the returns are hidden and resume as originally set up when the returns are shown. It is a major mystery to me. And I've never seen anything like it with Word. Any help with this situation would be greatly appreciated.

See More: MS Word Formatting

Report •

April 2, 2010 at 10:45:36

I have used Word for more years than I like to remember and I use section breaks and page setup (Landscape/Portrait) frequently, and I have never come across this.

Does this odd effect only occur with this one document, or has it started occurring with all documents.

If it is just this one document it is likely a corruption in the document - I have had odd effects occur with a single document, and after recreating the document it all works fine. I copy and paste sections at a time from the old to the new document, and keep testing that its working OK. Sometimes you can isolate where the corruption is, and then just re-type that paragraph or create a new table etc.

If this is happening with all documents, I would try a Word repair, (Help - Detect and Repair ...)


Report •

April 2, 2010 at 12:19:25
Humar, you're probably right that the document is corrupted. It's a different form of corruption that I'm not used to seeing. Generally, when a document can't differeniate between "Figures" and "Tables," I know it's corrupt. In this case it was so strange that I never considered the idea of it being corrupt. So, thanks.

Report •

Related Solutions

Ask Question