A thought about how you use your data, and how it affects 're'storage of duplicate data...
Why not instead have a "JPEGS" table with 5 records...your 5 jpegs in container...as well as a title field.
In your workflow, the user picks a title from the dropdown menu...and you use this choice as your link field to the JPEG table.
The container field from your JPEG table is on your layout and has an image as soon as they select the link field...
Does this accomplish what you are trying to do?
I suggest you consider creating a table in your solution dedicated to storing your images. If you set these to external storage and leave the storage location relative to the solution, then FM will create the folders it needs to store them. Once that is done you can access the images via a standard FM relationship rather than having to worry about external file paths.
Eric and keywords - great idea, so simple, never thought of using a simple "donor" table for images.