Thomas -

We create R:BASE output for use in Ventura Publisher, and I would make these
suggestions:

1.  Set all margins to 0
2.  Right-click on each section band and set to "Dynamic Height" (or remove
the band if nothing is in it.
3.  Create each line as one long variable and place just one variable on
each line of the report
4.  Click all the variable objects in the detail section and make sure they
are all the same size - then butt them right up to each other (rather than
leaving the extra spaces that you indicated)

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Sami Aaron
Software Management Specialists
913-915-1971
[EMAIL PROTECTED]
 


-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Thomas J
Hawley
Sent: Sunday, June 12, 2005 4:10 PM
To: RBG7-L Mailing List
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.
================================================

Reply via email to