Report

[faaslave]

I can not seem to figure out the report layout.

I have Regions, chapters, and members. I want a printout like below:

Region

ChapterNumber

Members listed

ChapterNumber Total members in that chapter

Subtotal for members in that region

Then grandtotal of all members at the end.

I made summary fields and tried several scenarios. None seem to work.

Help

Thanks, Dave

[-Queue-]

You have a leading subsummary by Region and a trailing by related region. Change your second trailing subsummary to be by Region. Then sort by Region, ChapterNum, and FullName, and enter Preview Mode.

[faaslave]

Thanks -JT-,

I changed it, now at the end I get total members.

There is still no breakdown by region or chapter.

Is it because there are fields from two tables?

Dave

[-Queue-]

There is a breakdown. Enter Preview Mode. Subsummaries aren't visible while in Browse Mode.

[faaslave]

Not on mine, even in preview mode

Dave

[-Queue-]

Make sure they are sorted. For a subsummary to show, records must be sorted by its break field. With all records found and sorted, on entering Preview Mode, you should see 50 on the second page for region AK, chapter number 358.

[Fenton]

Here's my version. I changed the Region in Members to be a Lookup on ChapterNum. All your Sort fields are in Members. I also made the layout multi-column (3), as you can get a lot more on the page that way.

FAAMA.11-08.zip

[faaslave]

I didn't see yours Fenton, I will download it and look at it. You and JT are probably going to start charging me soon.

I had it fixed for a sec, then it didn't work again.

These reports are ridiculous. Why are they so difficult?

I have attached the latest. I made two scripts to pull these reports up.

What I was trying to do was

show all records

find and omit chapter999

sort

preview mode

then it all screwed up. I tried to put it back and somehting is wrong now

Thanks for helping me

Dave

[-Queue-]

Check your sort. You're using related Chapters fields instead of the local Region and Chapter Num.

[faaslave]

Thanks JT

That worked, so I guess you can't sort from fields that aren't on the table that the layout is based on.

Please look at it now. I got it to work, but when I try to add an omit function, I don't want the corporate members in this report, It doesn't work.

Dave

[-Queue-]

You could sort based on related fields, but your subsummary parts would have to be based on the same related fields. The sort fields must include the subsummary break fields.

You are entering Find Mode and then entering Preview Mode without performing the find. Use Perform Find [Restore], instead, and specify Action: Omit Records when Members::Type with a criteria of Corp. Remove Show All Records and Enter Find Mode from your script.

[faaslave]

Thanks again JT,

Once I changed it to use the perform find[restore] it worked fine.

I made sure the sort came after, and presto.

I still have show all records before all this, in case the user already had a found set not inclusive of all records when they run the script. It works. Am I missing something by leaving it in?

By the way, I am going to start a post with a new issue, reference the hair DB, and this one might even be tough for the -queue-. Well maybe.

Dave

[-Queue-]

The Show All Records step won't matter, because you're performing a find. When you enter Find Mode, the found set in Browse is ignored. Perform Find [Restore] basically enters Find Mode, remembers the criteria, and performs the find. So even if you had no records showing, the find would still work.

You can leave it in if you prefer, but it's only wasting the time it takes to show all records.

[faaslave]

O.K. I was under the impression that if the user was, let's say looking at the members and already had a subset found, then ran the script, it would only start with those records. That is why I put that in there. But what you are telling me is that when a script is run, it will start with all the records anyway.

Thanks Dave

[Fenton]

You may be confusing Find with Constrain Find, which will restore the previous found set. Constrain Find will restore the previous found set, if the Constrain fails. This behavior is new to 7, and welcome, as long as you're expecting it.

[faaslave]

O.K. Find, starts with all records regardless of the found set you had when running the script, and Constrain Find, will use the found set you had when you run the script.

Thanks

Dave