Replies

Try turning off Tool-Options-View-Show Field Codes.

Many options are fairly self-explanatory. Even so, references to them are scattered throughout this Board.

For example,
“Don’t use HTML paragraph auto spacing” is explained in the discussion thread regarding Para Space Above.

Dear fburg

A couple of other tips:

Another good idea to avoid jumping of figures/ text boxes is to temporarily put a section break (Next Page) after the point where you do not want your pagination messed up.

If you have a grouped object which you want to ungroup without a messup, copy the grouped object to a new empty file based on the same template as the current one, do all the ungrouping there, and then after the object is done, come to the original file, put a section break as explained above at the end of the page on which you want to place the grouped object, and delete the original grouped object and replace it with the newly grouped object. After this is done, the section break can be deleted from Normal View.

Thanks, Geoff

You made my day!

Dear fburg

The macro is already posted on this board a few messages above. Geoff has moved the same to the VBA Board and also tweaked it and made it more effective and compact.

To ensure that your text box does not jump when you add/delete text on the page, before adding/deleting text, lock anchor of the text box to a paragraph which will certainly either begin or end on the same page even after the addition/ deletion. Also, uncheck the move with text box.

If by chance the text box has jumped to the next page, and you don’t mind the box on that page, but want to push back some text, then drag the object anchor to the next paragraph. As much of the earlier paragraph which can be accommodated on the earlier page will get pushed back, and the box will remain on the page it has jumped to.

Many Thanks for te tips.

I wrote the macro by merely recording macros and tweaking it to the extent necessary to achieve the effect I wanted.

Will certainly kee your tips in mind.

Many Thanks.

Controlling the height was a problem which I resolved by using Format-Font-Character Spacing. I shall now certainly try out the ADVANCE field option.

Actually the logic for the unending loop is that the Object is vainly looking for a Para Marker to anchor to, and cannot find it, because no paragraph either begins or ends on that page.

I have faced this problem umpteen times, and have figured out one explanation as to why it happens. I can induce the error at will with this explanation, and can also eliminate the error.

The first and commonest one is:

Word is trying to fit the graphic as well as the paragraph to which it is anchored on the page, and it cannot. So it goes to the next page, and tries the same and fails again, so it goes into a continuous repagination loop.

Why does this happen? There is apparently an undocumented requirement that at least one paragraph should either end or begin on a page. If there is, say, a paragraph which begins on Page 3, continues on Page 4 on which you are trying to place the object, and is long enough to continue on to Page 5, you will get the unending pagination loop.

What is the logic of this apparent assumption? I think Word assumes a paragraph to be smaller than a whole page. In this case, a paragraph straddling 3 pages militates against this assumption.

The solution? Just put a Section Break or a Paragraph Break (Enter) to break the length of the paragraph so it does not stretch to Page 5 (in this example). A Shift-Enter does not work.

If this explanation is actually correct, I will feel like Einstein.

This is not a problem with Word or your VBA elements, but with your Distiller settings.

You might be using Acrobat Distiller 4.0 with Press Optimised Settings, which means that if there is any font in the Word document which is not installed on your machine, Acrobat cannot embed the font in the PDF and hence quits.

Change the Acrobat Distiller settings so that it does not cancel job if embedding fails (Settings–Job Options–Fonts–When Embedding Fails–Warn and Continue).

Best way is to create an RTF file with each help topic separated by a hard page break, and compile this file after applying proper RTF Tokens (#, $, K, ! Footnotes in Word) using the Winhelp Compiler, and then use the HTML Help Workshop Conversion facility to convert the entire Winhelp Project into Compiled HTML Help. This way, you can get the best of both, Winhelp and HTML Help with very less effort. You can deploy either or both of them.

Access is more stable at these levels of records; further, you can always use SQL Queries to import selected data into Excel and also create Pivot Tables. Pivot Tables are the hammer with which you can hit every problem-nail.

Even better is to structure the data as a Pivot List and generate a Pivot Table to each user. File Size will be immensely smaller, giving much more utility.

Publisher offers Crop Marks, Color Registration Bars, Color Separations, Vertical Mirroring and several imposition choices, which Word does not, but is a lot more unfriendly.

True, Binder is the answer. I have used it and the only disadvantage is the rapidly ballooning file size. But it handles repagination and page numbering across applications it supports.