T
TonyW
I hope that someone can help with this, although I think
that the problem is a bug in the program.
I have a very standard report which contains numerous
memo fields set down the page. These memo fields are not
all that long (but usually greater than the 255 character
limit of text fields). I am using DoCmd.OutputTo
acformatTXT to save the report to a text file.
The problem is that the text file is not the same as the
viewed/printed report. Instead, Access dumps parts of the
memo fields in other parts of the document - most of the
lost text ends up at the end of the file, while other
bits find their way into empty fields. There doesn't
appear to be any pattern to where the text ends up,
excpet that the placement is replicable.
When I send the output to an RTF or HTML document, Access
seems to produce the output fine - hence, I think it is
the Access TXT filter that is at fault.
Any solutions or work-arounds would be welcome.
that the problem is a bug in the program.
I have a very standard report which contains numerous
memo fields set down the page. These memo fields are not
all that long (but usually greater than the 255 character
limit of text fields). I am using DoCmd.OutputTo
acformatTXT to save the report to a text file.
The problem is that the text file is not the same as the
viewed/printed report. Instead, Access dumps parts of the
memo fields in other parts of the document - most of the
lost text ends up at the end of the file, while other
bits find their way into empty fields. There doesn't
appear to be any pattern to where the text ends up,
excpet that the placement is replicable.
When I send the output to an RTF or HTML document, Access
seems to produce the output fine - hence, I think it is
the Access TXT filter that is at fault.
Any solutions or work-arounds would be welcome.