Matt,
Thanks for the reply. I will test your suggested method to see how it 'feels' to me. If nothing else, it will definitely be my fall back option.
I am considering my second option as a preference, as it may (if I can get it to work) enable me to have detailed text or HTML pages with not only textual information, but also multiple images stored and referencable from multiple albums, works etc, as well as from external apps.
This way I could have a detailed Bio, with multiple portraits, photos, art, ..., that are common across a composer or artist, and not require the images stored alongside the album files.
An alternative to this of course is for MC to store multiple images per file or even multiple images per field per file
So, I could have an image stored against the album name, one against the orchestra, one against the composer, ... you get the idea
oooh, and then, you could do the same for bio type information as well! The possibilities are endless!
[Edit]
Can this be done with some kind of
smartlist-to-<insert random field name> association?
[/Edit]
As an aside, I cant see how to add second image field to the library, not possible?
Cheers,
C.