** Reply to message from "A. Razzak Memon" <[EMAIL PROTECTED]> on Thu, 16 Jun 2005 08:51:20 -0400
Razzak, thanks for your reply. I hope I am not trying your patience. > Let me help you understand my replies and suggestions: > > 02. Make sure that you are using Build: 7.1.81.30505 or higher OK, the later build of 81 fixes the bug which was returning an inappropriate reference to the Print to Text File Setup. I can now use option ETXT in a command file. But the ETXT output is still corrupt: 1. The report consists of a simple report header (4 lines of FrameMaker ascii MML code) which prints fine, and then about 6,000 six line detail sections with about 50 two line break headers among them at various places. 2. The first 65 lines (the report header, two break headers, and nine details) print flawlessly. 3. Line 66 is a blank line (possibly the output is attempting to paginate? Is there a way to set an infinite page length, like we could do in DOS?) 4. We then have another page or so of flawless output. We come to line 132 (2 x 66) which is blank. 5. At this point, the output goes bad. We start to have numerous blank lines at random places, and random detail lines are skipped entirely. 6. Occasionally, there will be a run of ten or so detail sections that are flawless, but the corruption then returns. I can provide you with a copy of the database if that would be helpful. Something's just not right here. Tom Hawley New York [EMAIL PROTECTED]
