Tom:

>>>
I need a "Text File" (Option TXT) as opposed to a "Report Emulation
Text File" (Option ETXT).  TXT writes a clean ascii dump of the data,
with no pagination, margins, or formatting of any kind (what I need
for Adobe FrameMaker input).  ETXT uses returns and spaces to emulate
pagination and margins.
<<<
On my report I set all the margins to zero under page setup and I get a
long, plain file with no controls. If you need a plain file with no
formatting you should look into the UNLOAD command.

>>>
TENTATIVE CONCLUSION:  If you're going to specify an output file in
your PRINT command, do not specify one in Print to Text File Setup.
If you specify the same filename in both places, you will get a popup
print dialog.
<<<
FWIW, I use the same name in both places and I do not get the popup dialog.

Javier,

Javier Valencia
913-915-3137

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Thomas J
Hawley
Sent: Saturday, June 27, 2009 8:33 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: Eliminate Windows Print Prompt when printing to
Disk

Thanks Javier.

I need a "Text File" (Option TXT) as opposed to a "Report Emulation
Text File" (Option ETXT).  TXT writes a clean ascii dump of the data,
with no pagination, margins, or formatting of any kind (what I need
for Adobe FrameMaker input).  ETXT uses returns and spaces to emulate
pagination and margins.

As I read the documentation, you need to configure File > Print to
Text File Setup only for TXT;  this is not required for ETXT. I did
that, specifying a full path and filename ending with .txt; file type
= fixed length; and specifing the bands and the length of each.  The
report that is produced is exactly what I need.  I'm just trying to
eliminate the need to manually change the file type and filename in
the popup print dialog every time I run it.

In studying your message below, I noticed that you specify a .dat
output file.  I decided to try using that in my PRINT command, and to
my surprise it works!  No more popup print dialog!

I then went back to the Report Designer and in Print to Text File
Setup I deleted the filename, and in my PRINT command I changed my
output file back to .txt  This too works.

TENTATIVE CONCLUSION:  If you're going to specify an output file in
your PRINT command, do not specify one in Print to Text File Setup.
If you specify the same filename in both places, you will get a popup
print dialog.

The documentation of this feature needs to be rewritten.

Thanks very much for your reply which, in a roundabout way, was the
key to the solution!

Tom Hawley


[ Code for Print Routine: works without raising the print dialog ]

DELETE D:\_TEMP\DUMP_ARBS_2009.TXT
PRINT DUMP_ARBS +
  WHERE AWARD GE '3106' +
  ORDER BY ARBNAME, AWARD +
  OPTION TXT +
  |FILENAME D:\_TEMP\DUMP_ARBS_2009.TXT
-- Use LAUNCH to open in UltraEdit; |OPEN ON opens in Notepad
LAUNCH D:\_TEMP\DUMP_ARBS_2009.TXT


On Sat, Jun 27, 2009 at 12:48 PM, Javier
Valencia<[email protected]> wrote:
> Thomas,
>
> I use the print to text file option without any problems. Fist, on the
> report design screen, click "File" on the top menu bar, then select "Print
> to Text File setup..." and select the desired options on the setup window,
> including the file name.
> Then use a command similar to the one I use:
>
> PRINT W_distrep ORDER BY sub_sys ASC, seg_id OPTION ETXT|FILENAME
pciraw.dat
>
> W_distrep is thereport name and pciraw.dat is the name I selected on the
> Print to text setup window. You can, of course use your own WHERE and
ORDER
> BY clauses. It works for me and it should work for you.
>
> Javier,
>
> Javier Valencia
> 913-915-3137
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Thomas J
> Hawley
> Sent: Saturday, June 27, 2009 10:56 AM
> To: RBASE-L Mailing List
> Subject: [RBASE-L] - Re: Eliminate Windows Print Prompt when printing to
> Disk
>
> On Wed, Apr 22, 2009 at 4:07 PM, Ed Rivkin<[email protected]> wrote:
>
>> My problem is twofold. First I want to automate and bypass the Windows
>> "Print" setup.  I cannot seem to eliminate this despite having read and I
> believe followed
>> the cookbook instructions in "Printing Report as Text File". In addition
> the Windows
>> "Print" box pops up with "Print to File" already checked but it is
> defaulting to .pdf rather
>> than .txt.
>>
>> How do I force .txt and eliminate the Print box prompt.
>
> I'm having the same problem.
>
> The FTE document "Printing Report as Text File" (6 May 2005) in
> paragraph 11 gives clear instructions "to print to a text file without
> user intervention" but no matter what I try I always get the print
> dialog with PDF as file type and some other file name (not the one
> I've set in the "Print to Text File Setup") suggested.  I can change
> this to TXT and supply a different file name, and the report then
> prints exactly as it should, but surely there must be some way to
> automate this?
>
> Paragraph 11 states:
>
> ============
> 11. To automate the entire printing process, use:
>  PRINT ReportName WHERE ... ORDER BY ... OPTION TXT
> This will allow the report to print to a text file without user
> intervention.
>  The report will print to the filename specified in the Text File Name
> property, but the Print Dialog will not display the Print to File
> CheckBox or File... button.
> ============
>
> The functionality described does not seem to be present in 7.6.7;
> possibly this is how it once worked, and something became broken?
>
> I've tried deleting and recreating the report several times, but to no
> avail.
>
> There's another glitch in the FTE doc (and also in the substantially
> similar technical note in the Help's Reference Index) in paragraph 06
> which states "Click [Save Length] button to save the length for a
> selected column."  "Save Length" on this dialog is just a text label;
> it is not a clickable button.  The actual process for setting and
> saving a length is a bit of trial and error: enter a length value,
> click off the item, and then going back to see if the intended length
> setting actually took.  But eventually you can get it right.
>
> Tom Hawley
> Burke & Parsons, New York
>
>
>


Reply via email to