|
Home > Archive > MS Access data conversion > July 2005 > Problems with RTF conversion
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Problems with RTF conversion
|
|
| Sara Ferrarese via AccessMonster.com 2005-06-27, 7:24 am |
| Hi
I have some troubles exporting reports to RTF: some words are messed up.
My reports are something like
label text label
label text label
label text label
and so on.
When I export I get
text label label text label text
label label label
What can I do? Any help would be greatly appreciated
Thanks in Advance
Sara
--
Message posted via http://www.webservertalk.com
| |
| Chris Mills 2005-07-01, 3:25 am |
| As I recall, make certain aligned "things" are precisely aligned.
I don't mean "to the pixel". I mean to the precise same Top/Left (whatever is
appropriate) numeric value in the properties. Maybe even heights.
Otherwise the converter might think something is higher/left"er", and
therefore comes before something else in the report.
If this is true, I suppose you could put the things you want later, "a pixel
lower!"
Otherwise I don't know.
Chris
"Sara Ferrarese via webservertalk.com" <forum@webservertalk.com> wrote in
message news:507900F929004@w
ebservertalk.com...
> Hi
>
> I have some troubles exporting reports to RTF: some words are messed up.
> My reports are something like
> label text label
> label text label
> label text label
> and so on.
>
> When I export I get
> text label label text label text
> label label label
>
> What can I do? Any help would be greatly appreciated
>
> Thanks in Advance
> Sara
>
> --
> Message posted via http://www.webservertalk.com
| |
| \Sara Ferrarese via AccessMonster.com\ 2005-07-05, 7:24 am |
| Hi Chris,
I tried, but It doesn't work.
Actually the reports are much more complicated than what I wrote, much longer
and with subreports. Sometimes it's enough to put the part of messed up
report in a subreport, sometimes not (even if the only subreport is perfectly
exported). Maybe, is there a maximum length? the messed up part is quite
always at the end...
| |
| Chris Mills 2005-07-06, 3:24 am |
| I don't know.
I can't find any report I have which messes up in RTF (A2k2).
(except images in background or things overlapped really messes up)
I would be suspicious of putting anything in-line with a subreport.
I can't see max length being a problem. I've gone to some 20 pages/record with
expandable subreports.
You could see if forms work differently. (Forms can be used as reports)
You could try Bring-to-front/Send-to-back as a means of "ordering".
Forse dovete riscriverli appena.
Chris
""Sara Ferrarese via webservertalk.com"" <forum@webservertalk.com> wrote in
message news:50DC6C01C6980@w
ebservertalk.com...
> Hi Chris,
> I tried, but It doesn't work.
> Actually the reports are much more complicated than what I wrote, much
longer
> and with subreports. Sometimes it's enough to put the part of messed up
> report in a subreport, sometimes not (even if the only subreport is
perfectly
> exported). Maybe, is there a maximum length? the messed up part is quite
> always at the end...
| |
| Chris Mills 2005-07-06, 3:24 am |
| If items across the page have Can Shrink/Can Grow, I would set them
identically.
| |
| \Sara Ferrarese via AccessMonster.com\ 2005-07-06, 11:24 am |
| Subreports are not in-line with other texts, but when I export it lines of
the subreports are messed up with lines outside the subreport.
I noticed that exporting the report from the button instead of exporting it
from the module (using OutputTo) i get an overflow error (shouldn't they be
the same?).
forse dovrò riscriverlo da capo...
S.
| |
| Chris Mills 2005-07-06, 8:25 pm |
| > I noticed that exporting the report from the button instead of exporting it
> from the module (using OutputTo) i get an overflow error (shouldn't they be
> the same?).
>
One would hope so, but neither would I be surprised if (say) error-handling is
a bit different, since one is "manual" and the other is "automatic" of sorts.
It was a good test I might not have thought of.
Clearly, your report/RTF has (multiple) serious problems. At some stage, it
may be necessary to start the report again from scratch, and keep it simple. I
have sometimes spent many "happy" hours taking things out and putting them
back. If re-starting from scratch, I would not even copy/paste from one report
to another, if it's as troublesome as you say.
I note that sometimes I have 2 reports 1) For screen 2) For RTF/Word
conversion. Sometimes the required output is just different.
I would never discount the possibility of "corruption", either in the report,
or even in the test data you are using (which could explain a report only
getting so-far). But then, it's not my place to suggest general desperate
remedies, which you no doubt know.
As no-one else has responded, there does not appear to be a simple answer like
"do this!". Which may put some validity into my advice (start again, knowing
RTF can be tricky esp. if a report gets complex)
> forse dovrò riscriverlo da capo...
"Caution. Access can mess with your Head?" ;-)) ;-))
Chris
|
|
|
|
|