Report Printing Each Record on Separate Page

[Stanley - stanlyn-com]

Hi Ken,

>> So don't give filePro any sort information.
In the beginning, I didn't...  I started adding the sort stuff in an attempt
to get more records on a page.  I can do without the sort stuff.  The same
applies to the "f" and the "x" parameters, as I don't need them...

>> Except for @T4, all of those will *not* print in record number order. 
>> (Unless every record was updated on the same date, or last update [or
created by] the same person.)
With no sorting set, I would expect them to print in record/natural order
using only the records that matched the selection criteria.  Am I thinking
correctly here?

>> The "f" will force a page break.
Yes, I know.

>> You say you don't need to have it sorted, so don't.  Leave the sort
information blank.
I originally left it blank, and I only get one record per page, then I
started messing with the sort stuff, again I don't need it.   

>> And, what you mean by the order they were "created or updated"?  If I
create records A, B, and C, and then update B, what order do you want?
A,C,B in your example.

>> If you are only getting one record per page, then you have done something
to tell filePro to do so.
The only places I know that controls this is "the sort" screen and "page"
commands in processing.
 
>> What is the exact sort information you currently have?
None, and still only printing one record per page.

>> Do you have any PAGE commands in processing?
No.

Thanks, Stanley





-----Original Message-----
From: Kenneth Brody [mailto:kenbrody at spamcop.net] 
Sent: Monday, April 09, 2012 5:43 PM
To: Stanley - stanlyn-com
Cc: filepro-list at lists.celestial.com
Subject: Re: Report Printing Each Record on Separate Page

On 4/9/2012 4:46 PM, Stanley - stanlyn-com wrote:
> Hi,
>
>
>
> Using FilePro Sco Unix 5.0.14d4, I need the report (which was the 
> option 1,
> Report) to print more than one record per page.

Unless you tell filePro otherwise, it will print as many records on a page
as will fit.

> There is no sorted needed
> as they need to flow in natural/record # order.

So don't give filePro any sort information.

> I have tried using the @u4,
> @t4, @ub, and @cb fields separately

Except for @T4, all of those will *not* print in record number order. 
(Unless every record was updated on the same date, or last update [or
created by] the same person.)

>  to create a sort on that with both an "x" and an "f" in an attempt to 
> get more than one record per page.

The "f" will force a page break.

> I was
> thinking it had something to do with the sort and should be pretty 
> straight forward, but I guess not.

You say you don't need to have it sorted, so don't.  Leave the sort
information blank.

> I'm needing to print a report for a specific user on a specific day in 
> the order they were created or updated.

In that case, you *do* need a specific sort order.  However, unless you have
a field containing an incrementing value, there is no guarantee that all the
records will come in the order you want.

And, what you you mean by the order they were "created or updated"?  If I
create records A, B, and C, and then update B, what order do you want?

> This is
> somewhat like an audit of a users work.  I have everything working 
> except it wants to print only a single record per page thereby wasting
paper.

If you are only getting one record per page, then you have done something to
tell filePro to do so.

What is the exact sort information you currently have?

Do you have any PAGE commands in processing?

--
Kenneth Brody