List of names without duplicates...

[NBL]

I'm using filemaker 6 for this project. this is a billing database where billing information is tracked on a weekly basis. made searchable by "week ending" date. one person will be billed multiple times a week, month or year. so for their info we have fields "lname", "fname", and "id" per se. if i make a layout with those three fields in a row, and do a list, i get all their names, but for EACH and every record.

what i need is a list of current people being billed (by just doing a find for a certain date) and then listing all names with id's however, don't need 67 sally jones in the list. i only need 1 sally jones, and so forth, tom smith, etc. if anybody could shed some light on this it would be greatly appreciated. i tried to do subsummary parts but that didn't seem to work, maybe im doing it wrong?

thanks!

nbl

[NBL]

If i am in the wrong section please let me know!

[Ender]

A columnar report with sub-summary parts is a good way to go. In your sub-summary report, if you have the Body part in there, each record from the found set will show, including duplicates.

What you should do is replace the Body part with a Sub-Summary by ID part. Fields on this part will show up when the found set is sorted by ID and the results are printed or viewed in Preview Mode.

What I would do is sort it by LName, FName, and ID. This puts them in an order that makes sense for humans, but still shows the sub-summary part.

You may be asked to build a similar report showing the individual bill lines under each person's name (I know how management likes to add these things.) This can be done by adding a Body part back in, and putting the billing details on that part.

You might also be asked to add other breakdowns by Week or Month or Year. These can be done by adding a Sub-Summary part for whichever, and sorting by that field.

The nice thing about sub-summary parts is you can have multiple sub-summary parts on the same layout, and the only ones that show are those that are included in the sort order. This can make it pretty easy to build reports that are flexible to the users' needs.

[NBL]

Thanks for the input. i'll give it a try.

[NBL]

Thanks Ender, that worked perfectly!