Print Repeated Values

[AndrewMozley]

Using the report writer to print a report from a single cursor.

The report is a list of invoices, each of which may have more than one line. So I am printing Invoice reference, Supplier name and line value (and some other things). The report is grouped by invoice reference (within date).

For a multi-line invoice I would prefer not to have the supplier name (and indeed the invoice reference itself) repeated on the 2nd line. However when, in the report designer, I double click on the 'Supplier name' field and go to the 'Print When' tab, the "Print repeated values" options are greyed out.

I do not have anything specified in the 'Print only when expression is true' box.

How can I suppress the repeated values? Have searched other sites for references to this matter, and it seems to have occurred to many people.

I suppose I can process the cursor (before running the report) and blank out the repeated values but would prefer to use the feature in the report writer.

Thanks. Andrew

 

[Mike Lewis]

Andrew,

As far as I know, the only time those options are greyed out is when the field is in the title or summary bands. Could that be the case?

They are also greyed out when the 'Print only when expression is true' box is not empty, but you have already said that is not the case.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads

 

[AndrewMozley]

No. In fact my groupings are 1. On .T. (because that is how I get a grand total), and 2. on InvRef.

The item (cdata.name) that I cannot ask for suppression of repeated values is in the lowest level group, that is just before some things get totalled on invref.

Curiously I noted that on the same line of the report I have a field cdata.desc which can have repeats suppressed. So I have changed that to cdata.name and asked for that to be suppressed.

When I preview the report, the second (RH) occurrence of cdata.name is indeed suppressed on the second line!

I have examined the .frx file as a .dbf and tried to spot the difference between the two records. there were some, but even when I patch the records to be the same, the problem lingers on. I will persist!