You might just need to populate display fields programmatically.
I think that what you have is what I call a "Public table" ... a table with one record containing non-global fields.
Displaying data is one of the few times where repeating fields are truly useful - especially if you need rows/columns of data that can't be dealt with via normal FM views (see my Surrender to Fun, with FileMaker for "mad" use of repeating container fields).
A portal for messages makes the most sense to me. A popover in the portal row can show an expanded view of the message.
You can make a cartesian join (shows everything) and this isn't a hack it is just another way to show data. A portal would then be a fine option. The cartesian join is the X type join. On top of that you can just use fields like 1 = 1..