** Reply to message from "A. Razzak Memon" <[EMAIL PROTECTED]> on Wed, 15 Jun
2005 23:00:16 -0400
> Using the latest pre-release update 81, if a user attempts to
> PRINT the report as Text File (OPTION TXT) without first having
> defined the Text File Setup in Report Designer, the program will
> return an -ERROR- message and not just write a zero length file.
Razzak, Stephen Markson was trying to run ETXT (not TXT).
1. As I understand it, Text File Setup is relevant only to the TXT output
option. ETXT prints the entire report, so there'd be no point in trying to
specify bands in Text File Setup. While your 6 May 2005 FTE document
("Printing Report as Text File") does not say this explicitly, that's certainly
my interpretation.
2. Both options use the same .TXT filename extension, but the report output
options are EXTX and TXT.
3. I'm using Pre-Release 81, build 30502. You fixed the zero length file
problem after I reported it in April, and in the discussion that accompanied my
issue it became clear to me that what I should have been using was ETXT, not
TXT.
4. My Text File Setup is empty; nothing's been defined there. So why, when I
am attempting to use the ETXT option in a command file, do I get an error
message:
-ERROR- No Controls Specified For "ETXT" Option. Go to "File->Print to Text
File Setup..." in the Report Designer
Here's the relevant part of my command file:
PRI D05_GEO where DOD is null +
order by zip_5, lastnam, firstnam, adr1 +
OPTION ETXT +
|FILENAME E:\ORCIS_PR\GEO_DUMP.TXT +
|OPEN OFF
I can run the same report using the Reports > Run dialog. But it won't work in
a command file. So that's a bug, I think?
5. And finally: The ETXT report is seriously corrupt, with missing lines,
clipped data, etc. The first two or three pages of data are good, but then
the corruption sets in. The report is useless.
Tom Hawley
New York
[EMAIL PROTECTED]
