report grouping questions

RE: report grouping questions

Shelly-the calc field worked great and saved me a lot of effort on the release of an update disk. THANKS!!

RE: report grouping questions

Thanks, Tom & Shelly, for your suggestions.

Tom-I had already thought of a way I could use your method. I was just being lazy and wondered if there was a way I wasn't considering to modify my existing report.

Shelly-I'll give your suggestion a try and see what happens. Thanks!

[Tom Cone Jr]

RE: report grouping questions

Shelly, yes, I see that now. However, I understood that any one customer might have several different records, in some of them the customer would be responsible as ow, in others the same customer would be responsible as ap, etc.

Guess I'm off base, so I'll hush up.

-- tom

RE: report grouping questions

Tom,
Forgot to add that this group break calculation would then 'bunch' the records on the calculated customer id, not by ow, op, ap.

Attached is a small app showing how I did this.

Shelly

RE: report grouping questions

Tom,
The result of the calc field would be a customer id. Based upon who is paying, it would be the id of Owner, Operator, or Applicator. I did make another assumption; that there is only one id per person/address irregardless of how that person can be classified (ow, op, ap).

In creating the group break, for 'break on change in' choose 'expression' and put this calculation in the expression builder.

Shelly

[Tom Cone Jr]

RE: report grouping questions

Shelly,

I fear it's going to be more difficult. Wouldn't your approach 'bunch' (a technical term) all the 'op' records together, all the 'ow' together, and all the 'ap' together? I think Becky wants the group break on the customer name or id, and to include all records where this person is responsible for a bill, whether they happen to be an op, an ow, or an ap.

Becky,

you might investigate creating a temporary table, that can be thrown away after the report is run. In the temp table populate it by stepping through the real table, and copying over to the temp table one record for each responsible customer, regardless of whether they're an ow, an op, or an ap. Base your report on the temp table.

-- tom

-- tom

RE: report grouping questions

Becky,
I would create a display calc field based on who is being billed. Assuming:

Owner id is custid1
Operator id is custid2
Applicator id is custid3
if for some reason user entering the salesform doesn't select someone to bill, bill the owner

the calc field would look something like this

case(bill="ow",custid1,bill="op",custid2,bill="ap",custid3,.t.,custid1)

Then I would add a group break on this calculated field.

Hope this helps.
Shelly

I am designing a billing statement report to print when a customer's balance due > $.10. Three people are listed on the salesform (owner, operator, applicator). The user chooses (via a radio button) which person is billed for this sale. The button choice fills in either "ow", "op", or "ap" in a field called "bill" on the salesheader table. I want the billing statement to total the amount owed on any number of salesforms by an individual, whether he be an ower, operator, or applicator.

I had a simpler billing statement in the past where the owner was always billed. On the report, Group1=custid1, Group2=salesform no. The report summarized each ticket owed and gave a grand total.

Now I'm not sure how to group or filter the statement so that all charges still print to an individual, whether he be custid1, custid2, or custid3. I have thought of a couple of solutions which involve table reconfiguration, but this needs to go out to 20 long-distance users (on Runtime) and I really don't want to deal with their data. Can someone think of a way to change the grouping/filtering on the report only to accomplish this?