Truncation of Access Report after export to RTF

[Composer]

This is not a question but rather an answer, or at least a clue.

Like others, I had experienced seemingly random truncation of text
when exporting a perfectly good Access report to RTF. Or rather, one
person experienced it when another didn't, running the same database
on the same computer, both accessing it via Remote Desktop Connection.

This problem made no sense until we found that we had different screen
resolutions, and that when we changed screen resolution (on the client
computers) the resulting RTF export (on the host computer) changed.

I have no science to offer. A resolution that worked on one monitor
would cause problems on another monitor with a different physical
size. So experimentation seems necessary. But the surprising fact is
that Access may export something different to RTF depending on your
screen resolution.

One factor may be our use of fTextWidth in the VB code behind the
report. Maybe. It would be too much work for me to try to reproduce
this problem after changing our report. So I can only suggest that if
you have the problem, experiment with screen resolution.

Notes sent to my e-mail address are automatically deleted.

[Composer]

Further to the above, I put some Debug.Print into the fTextWidth code
to find out how different screen resolutions affect the computation of
text width. There was no difference at all. Therefore I don't see a
way to control this behavior using VB code. The bug is somewhere deep
in Access.

[Rick Brandt]

Composer wrote:

Further to the above, I put some Debug.Print into the fTextWidth code
to find out how different screen resolutions affect the computation of
text width. There was no difference at all. Therefore I don't see a
way to control this behavior using VB code. The bug is somewhere deep
in Access.

It's been there forever. It's not fixable. The RTF option is only suitable
for simple tabular output. Anything with growing text will have this
problem. It's just a matter of degree.

Use a PDF writer instead.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com