[Lawrie]

Ok ... I came to the same conclusion as you, but figured I'd ask incase I was overlooking something. I'll probably end up breaking up the book as individual songs and associating each set list with the specific song for the week.

This is how I approach this very problem (using the methodology that I believe is intended to be used in MS):

1. I create a csv file and import the csv into a collection (specified in the csv).  This collection is specific to the songbook*.
   
2. In the csv I specify the song number for inclusion in the "Custom" field.
   
3. As a result, all the songs in the songbook have an entry in the database, BUT there is only one pdf in use.  No messing around creating separate pdfs etc..
   
4. In MS Settings | Library Settings I have the Song title Formatting set to:
   %TITLE% %CUSTOM:[$(CUSTOM)]%This adds the contents of the Custom field to the displayed song title if it is not empty.
   
5. When I create a setlist, I simply specify that collection in the filters to limit choices and then add the required songs to the set list.  I can also search on name or number.
   

Voila! The set list entry picks the right song every time.
Takes a little longer to do the initial setup as the csv has to be created and imported, but this only needs to be done once, and you never have to search through a large pdf looking for a specific song again.


* I give the collection the same name as the songbook.  If the songbook is transposed for, say, trumpet, I will include the transposition in the name I give the pdf, and hence also the collection.