Unfortunately I have heard of this issue before. It only seems to happen
when you are building RTF strings on the fly.
There is no resolution. All other RTF controls instantiated from the MS
RTF DLL's suffer the same issue.
The last person who asked me to look at this issue was a very nice
developer from Germany I think. He was going to contact me if he ever
found a workaround but I have not heard from him.
Since the issue sounds like it may be internal to the RTF
control(wiothin it's source code) there is no direct solution. But I'd
like to try something just to make sure the RTF strings you are building
are syntactically(is that a word?) correct.
Send me a sample MDB that demonstrates the issue. I will add code to
copy your RTF strings to the Clipboard and then Return them before
insertion into the control. The Clipboard object will tell us two
things:
1) I will view the Clipboard contents directly to check for the Bug.
2) I will compare the RTF string returned via the Clipboard to your RTF
string for any differences.
--
HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
> Unfortunately I have heard of this issue before. It only seems to
> happen when you are building RTF strings on the fly.
[quoted text clipped - 27 lines]
> Access Code, Tips and Tricks
> Please respond only to the newsgroups so everyone can benefit.
Hi Stephen,
I've been working on it more since this afternoon. I think I've
convinced myself that it's not the RTF string after all...
Rather than hack code out to send you, I just did some clipboard
experiments myself (thanks for the suggestion). The same strings
(from the merge table) that print wrong on the access report, print
fine elsewhere.
I went back and started looking at formatting issues after that.
As I mentioned before, the first two labels on any page are always
correct, so I got me wondering. I changed the report so that only
one label shows up on each page. They all print correctly that way.
I've done about everything I can think of around sizing of the
control and the detail section, but nothing seems to alter the
errors. It seems related to how the RTF controls are grouped on a
page... More than two, and the errors begin.
Any thoughts on this line?
TTFN, Max
Hi Again Stephen,
I was looking around MSDN for clues, and found something about text
widths being calculated differently when saving to a .txt or .rtf file. It
didn't really seem to apply to my issue, but it made me reflect that I've
never tried different fonts to see what happens.
I've been using MS Sans Serif all along. I switch to another font,
and VIOLA! Everything printed correctly! I have a billion fonts on here,
and have only checked a few. Here's a sampling:
TT Verdana Regular good, Bold bad
TT Times New Roman All Bad
S Sans Serif All Bad
A Lucida Sans All Good
O Garamond All Good
S Fixed Sys All Bad
O Courier New All Good
O Ariel All Bad
where 'O' and 'TT' are true type, 'A' are adobe fonts, and 'S' are system
fonts.
I'll keep looking into things, but I'm getting close to parts of the
system that are "magic boxes" to me, like character formatting and such.
If this extra info sparks any thoughts with you, I'd sure like to hear
them.
TTFN, Max
Stephen Lebans - 21 Nov 2004 23:14 GMT
Excellent Max! I'll post your findings on the RTF2 web page.
:-)
--
HTH
Stephen Lebans
http://www.lebans.com
Access Code, Tips and Tricks
Please respond only to the newsgroups so everyone can benefit.
> Hi Again Stephen,
>
> I was looking around MSDN for clues, and found something about
text
> widths being calculated differently when saving to a .txt or .rtf file. It
> didn't really seem to apply to my issue, but it made me reflect that I've
> never tried different fonts to see what happens.
>
> I've been using MS Sans Serif all along. I switch to another
font,
> and VIOLA! Everything printed correctly! I have a billion fonts on here,
> and have only checked a few. Here's a sampling:
[quoted text clipped - 12 lines]
>
> I'll keep looking into things, but I'm getting close to parts of
the
> system that are "magic boxes" to me, like character formatting and such.
> If this extra info sparks any thoughts with you, I'd sure like to hear
> them.
>
> TTFN, Max