[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 252
  • Last Modified:

MSWord 2003 Can not insert page breaks

I have a MSWord 2003 document, generated by our web site (using vanilla ASP code - where unfortunately MSWord does not recognize the  ASP page break command).   Therefore we would like to insert the page breaks manually.  When doing this, the page break does not insert itself where we would like it to insert (by company name - with the black background) but throws it to the top of the document.

The document was first manipulated:
1. By removing the Top Heading
2. Maximizing the left and right margins
3. Converting Table to Text > Separate text with Tabs Search-output.doc
0
GeorgeJacobson
Asked:
GeorgeJacobson
  • 2
2 Solutions
 
regmigrantCommented:
at some point during the reformatting, probably the Table to text part but possibly because of the way the web site is formatted you have wound up with a series of nested tables so you the (obvious) table is actually sitting in a cell in a row within another row.
You can see this if you select the whole lot (Ctrl-a) and use a table format to highlight the various rows etc - those 'cells' out to the right are actually the ends of the rows of the outer tables.

I deleted all the extra columns and rows I could find, then selected each company section and cut/pasted it to its own page but if you can find out where the nesting is coming from their wil be a faster way


 Search-output-1-.doc
0
 
GeorgeJacobsonAuthor Commented:
Thanks alot!
We are working both your solutions right now.
1. Removing the nested tables manually
2. Coding the ASP so that it does not create nested tables

Will let you know asap.  Much obliged!
0
 
Paul SauvéCommented:
Hi,

What I did was to select the entire table then use the Convert table to text and deselecting Convert nested tables. I repeated this two more times and ended up with the following file (a series of 11 tables which I numbered): Search-output-2-.doc

This method is a bit quicker than the above "brute force method"
0
 
GeorgeJacobsonAuthor Commented:
We changed the ASP code to only a single level of tables (Removed all nested tables).  As a result, when in MSWord, the option to convert Table to Text was no longer available.  We could then enter page breaks without any problem.
Thanks to both of you!
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now