what you're asking for sounds really straightforward but I may be misunderstanding your question. Could you post one of the tables so that we can see what you're working with?
Doesn't sound straightforward at all.
Sounds like a mind-reading exercise.
How is it not a layout?
What if you can't sort it?
What if you want it to appear in a certain font or position on the page?
Which fields should be presented, and which should not?
How is the selection of data chunks which should appear, not a layout?
If I present something to you and tell you, it's done.
Here's your answer
And you say no, that's not what I meant. I really I need this and this and this... How is that not a layout design?
If we made a list view and just say, well call it something else?
Wouldn't that be the same thing?
One the one hand, you describe a list view layout and then you say that you don't want a list view layout. Either you don't understand what can be done with a list view layout or you are requesting something more than what I am reading from your original post.
A list view layout for example, can produce this type of report quite easily:
and so forth....
Thanks for the rapid response guys. I apologize for the vague question. If I'm understanding the way FileMaker works, I may be looking to implement something resembling a Dashboard, which right now is a bit above my skill level.
I'm still wrapping my head around the concept of a layout being a visual representation of a table as opposed to being a blank canvas to throw data on.
Dashboard type layouts are common in FileMaker solutions. Placing portals on such a layout is often done as a way to list multiple records from a table on such a layout. If you want to list all records from such a table, you can set up a Cartesian join using the X operator instead of =.