V
vabki
An application produces a number of reports, which are saved as text files
(using DoCmd.OutputTo acReport, stDocName, acFormatTXT, "filenamex.txt") each
of which is transferred to our mainframe where they are stored for long-term
viewing. Some of the reports have no spacing issues, but those with a
significant number of fields are having some fields truncated, because, in
the .txt file, there is white space (added by the outputto) between fields,
causing the report to be too wide when it gets to the storage facility. The
storage facility always treats stored reports as if they were built using a
10 cpi fixed width font.
Is there any predictable relationship between the font, spacing, field
widths, etc from the report in designer and locally printed mode versus what
is created when the outputto...txt... command is executed?
Thanks in advance for any assistance.
(using DoCmd.OutputTo acReport, stDocName, acFormatTXT, "filenamex.txt") each
of which is transferred to our mainframe where they are stored for long-term
viewing. Some of the reports have no spacing issues, but those with a
significant number of fields are having some fields truncated, because, in
the .txt file, there is white space (added by the outputto) between fields,
causing the report to be too wide when it gets to the storage facility. The
storage facility always treats stored reports as if they were built using a
10 cpi fixed width font.
Is there any predictable relationship between the font, spacing, field
widths, etc from the report in designer and locally printed mode versus what
is created when the outputto...txt... command is executed?
Thanks in advance for any assistance.