Thomas
Is there a reason you can't output to PDF file, which I'm sure Adobe
Framemaker can read?
If not, Is this email Razzak sent to you on April 30 relevant?:
"Tom,
In order to PRINT the report as "Text File", first you need to
identify the "Band" to be included for text file. If there is
no band defined, you are going to get the zero byte file.
Here's how to use the "Print to Text File Setup ..." :
01. Report Designer | File | Print to Text File Setup...
Notice the following options:
File Name:
File Type:
Bands:
Available Controls, Select Controls, Save Length
02. Select the File Name: (Click on [File] Button
Example: TestFile.TXT
03. Select File Type: Fixed Length
Options: Comma Delimited, Tab Delimited, Fixed Length
04. Select Band: Detail
05. Select Column(s) from the list of Available Controls
06. Customize each selected column and make sure to define Length
(Save Length).
07. Click on [OK] button to save these settings when using
Print to Text File.
Along with other report settings, these settings will be saved
with the report.
Repeat step 06 to define the length for each column, if necessary.
All of these property settings prepare the report to be printed to
a text file.
08. While still in Report Designer, Select Report Preview.
Click on "Printer" icon
Check "Print to File" Option
You'll notice the Type "Text" and the Text File Name as defined
in Step 02 above.
The print dialog will then display a Print to File CheckBox and
File... button (so the user can change the file name specified in
the Text File Name property.)
Click on [OK] button to print the file as TEXT.
09. Close the Report Designer or simply Click on R> Prompt icon from
the Tool Bar.
10. At the R> Prompt, type:
DIR TestFile.TXT
Notice the size of TestFile.TXT file.
To view the entire text file, type:
LAUNCH TestFile.TXT
Take a look at the File using MS NotePad.
That's all there is to it!
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.
For complete details on PRINT command:
From The Edge: http://www.razzak.com/fte
Topic: Using Enhanced PRINT Command in R:BASE 7.x for Windows
12. Got R:Docs?
Let the R:Docs help you define the entire PRINT Syntax for you.
13. Take a look at the sample application to demonstrate the use of
Printing Report to Text File.
http://www.razzak.com/SampleApplications (Item 002)
Enjoy and make sure to have fun!
Very Best R:egards,
Razzak."
David Blocker
[EMAIL PROTECTED]
781-784-1919
Fax: 781-784-1860
Cell: 339-206-0261
----- Original Message -----
From: "Thomas J Hawley" <[EMAIL PROTECTED]>
To: "RBG7-L Mailing List" <[email protected]>
Sent: Sunday, June 12, 2005 5:09 PM
Subject: [RBG7-L] - Text Dump Issues
> I need to dump certain contents of a database in plain ascii format, and
apply
> formatting tags to it. The dump file is then tweaked a bit in a text
editor,
> and loaded into Adobe FrameMaker for final production. This could be
easily
> accomplished in RB DOS with simple reports, but I'm finding that it
doesn't
> work so well in RB 7.81 where the reports have a graphical aspect that
gets in
> the way.
>
> The problems:
>
> 1. Blank lines appear in the dump at seemingly random places
>
> 2. Some data is clipped (e.g., "John Smith" might appear
> as " ith"), again in seemingly random places
>
> 3. Occasionally an entire line will be dropped entirely
>
> 4. Occasionally the dump will be corrupted in places
>
> My dump report uses only a report header, a break header, and a detail
section.
> Here's the scheme:
>
> RH Label
> BH Label (Formatting tag A)
> BH DB Text
> D Label (Formatting tag B)
> D DB Text
> D DB Text
> D DB Text
> D Variable Label (some concatenated DB Text)
>
> It seems that by allowing plenty of vertical white space between the five
lines
> in the detail section, I can eliminate the clipping, dropping and
corruption.
> However, this increases the number of random blank lines. And I'm left
feeling
> uncomfortable with the integrity of the output.
>
> I'm using the following command to print the report:
>
> PRI D05_GEO where DOD is null +
> order by zip_5, lastnam, firstnam, adr1 +
> OPTION TXT +
> |FILENAME E:\ORCIS_PR\GEO_DUMP.DMP +
> |OPEN ON
>
> (I notice that when I print to a file, the file does not contain page
breaks,
> although the progress dialog is counting pages. There doesn't seem to be
any
> way (or perhaps any need?) to set a continuous length file. I've got the
> margins set to 0 and that seems to work OK.)
>
> Surely there must be some way for RB to just spit out clean, simple and
> error-free tagged ascii text the way it used to. Am I missing something?
>
> Many thanks.
>
> Tom Hawley
> New York
> [EMAIL PROTECTED]
>
> --- RBG7-L
> ================================================
> TO POST A MESSAGE TO ALL MEMBERS:
> Send a plain text email to [email protected]
>
> (Don't use any of these words as your Subject:
> INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
> REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
> ================================================
> TO SEE MESSAGE POSTING GUIDELINES:
> Send a plain text email to [email protected]
> In the message SUBJECT, put just one word: INTRO
> ================================================
> TO UNSUBSCRIBE:
> Send a plain text email to [email protected]
> In the message SUBJECT, put just one word: UNSUBSCRIBE
> ================================================
> TO SEARCH ARCHIVES:
> Send a plain text email to [email protected]
> In the message SUBJECT, put just one word: SEARCH-n
> (where n is the number of days). In the message body,
> place any
> text to search for.
> ================================================
>
>
