Did you try a sorting a sub-summary part by song first, then a sub-summary by composer. Or sort sub-summary by song, then put composer in the body.
Don't forget to perform a sort after making the changes.
What you have is a many to many relationship. A composer can write more than one song and a song can be written by more than one composer. This will require 3 related tables: Composers, Composer_Song, Songs.
Start with these relationships:
Composers::__pkComposerID = Composer_Song::_fkComposerID
Songs::__pkSongID = Composer_Song::_fkSongID
You can place a portal to Composer_Song on the Composers layout to list and select a Songs record for each given Composers record. Fields from Songs can be included in the Portal to show additional info about each selected Songs record and the _fkSongID field can be set up with a value list for selecting Songs records by their ID field.
With that set up, you can create a Creating Filemaker Pro summary reports--Tutorial with a layout based on Composer Song to list each song and the composers who wrote it.
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
wow! I could NOT come up with that, myself!
Nice with some new angles of FM Pro!
(been an on n' off user since a looooong time - it's changed a bit since last time : D - I'm on FM Pro 10 now - perfect for my needs!!)
Thanks for help.