PROBLEM:

I have a report in access that is a fairly sophisticated merge of
multiple fields across multiple levels in my MS Access database
(Access 2000). It looks gorgeous!

When I export this report to MS Word (Word 2000) using 'Tools' -
'Office links' - 'Publish it with MS Word' - some of the lines in the
report are truncated. The report is made up of primarily titles of
presentations for a conference. Titles of a certain length get
truncated. Short ones are not truncated (roughly 8/10 of a line or
less) and long ones are not truncated (going on to two lines) - only
those that are approximately a full line long have the final word or
two cut off and those words do not appear at all in the word document.

Details:

1. It never cuts off part of a word - only an entire word or words
that appear at the end of a line

2. This appears to happen regardless of the font, font size, or
margins. I have experimented with the margins extensively (although I
am open to a concrete response that might involve margins) and it did
not help to have the margins exactly the same on the report and the
word document or larger on one and smaller on the other (tried each
variant).

EXAMPLES:

"Welcome, State of the Association, Presidential Strand Overview, and
Presidential Address"

is shortened to

"Welcome, State of the Association, Presidential Strand Overview, and
Presidential" - the "Address" that would fall at the end of the first
line on the MS Word page has disappeared (no it is not hiding in the
margins, it is gone!).

"Maintaining Independence: Balancing Client Needs with Professional
Standards of Evaluation Practice"

is shortened to

"Maintaining Independence: Balancing Client Needs with Professional
Standards of" - the "Evaluation Practice" has disappeared

CONTEXT AND CAVEATS:

Please note that it is not feasible for me to make this document
directly in Word - the level of sophistication needed for the merge,
using multiple levels, is not available in word - at least at my level
of expertise (and I need an answer that I can actually implement).

I know that I can address this by a painstaking review and hand-typing
to edit the word document. However, this is a process that I use
regularly and the word document that is produced, each time, is
150-200 pages. The time needed to hand-edit is extremely long.

Thanks to any and all who can provide a concrete, feasible, answer and
save my sanity! - Susan

Here is the issue:
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q125/6/49.asp&NoWebContent=1&NoWebContent=1

I sympathize with your frustrations.  We frequently export our Access
data out to Word via RTF and I constantly have issues with it chopping
off at the end of the line as well.  I do not agree with stevbe's and
Microsoft's solution, however; if you change the textbox widths and
heights you may solve the truncation problem with the specific record
that you are looking at, but it may create new ones with other
records.  With multiline fields, it depends on your specific record
and where the text in that field ends.  If it's close to the end of
the textbox, it's gonna chop off.  I've done extensive research in
this area and here are possible solutions I encountered:

1. Go to the Microsoft website and review this document for tips on
how to create reports that will export nicely.  Unfortunately, the
rule of thumb here seems that the more basic you can keep the reports,
the better they will export out.  If your data is complex like mine
is, you won't like their suggestions and they won't necessarily help:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;q130857

2. As you mention, a mail merge is possible if your data is not
GROUPED more than one level.  This is the solution we use where most
of the data is exported on a record-by-record basis.  My mail merge is
set up to group by one field and then show each record under it before
going to next group field.

3. Create a report using VBA code.  This is time-consuming, but it
depends how important the report is.

Also:
Try this link:

  http://www.lebans.com/ReportUtilities.htm

  there are some VERY interesting items here.

I suggest you go to the Microsoft Homepage and seek for help but try
rephrasing your question.

I am sorry for the delay. I cannot thank you enough - just for helping
to confirm that the problem exists for others and was not somehow a
function of my own faulty report. As a note to the second responder, I
have tried, and failed, to seek help on the microsoft list.

I am going to try the rtf software suggested on the page to which you
linked me. Again, my thanks - I am more than happy to pay you, cdc,
just for getting me this far.