I don't think it's entirely farfetched to want to show data in a grid format like that. Access doesn't make it easy to do so, though.
The problem with this situation (normalization/best practice issues aside) is that it's not easy to create controls on the fly. In fact, if you plan to distribute as a *.de file, you simply aren't allowed to. This leaves options of:
a) use a UserForm from the MSO library, where you can create controls on the fly (this is how the All-VBA treeview was done). This is not usually desirable due to the added dependencies and difficulty binding/interfacing with native Access behaviors. Or:
b) create a whole boatload of controls (which serves as a max amount also), have them hidden by default, and dynamically bind, arrange and set visibility as required. This is a viable option if you know you'll never have more than X number of controls (and if X is a reasonable number), but takes a lot of programming. Or:
c) create a single "row" as a continuous form, with as many "columns" as you'll need displayed. Create a special query that forms the data as required into the number of "columns" you have, repeated as required. This is often preferred as you can be truly dynamic to show hundreds or thousands of rows, but is the most difficult to set up. Such queries are tricky, and formatting of the last few controls can be difficult as well (for example, if you have 5 "columns" per row, and 48 records, the last row shows 3 records, so you need to "hide" the last two column controls without interfering with the rest of the rows: this can usually be done via conditional formatting and an overlay, but isn't always easy to do).
At UtterAccess, Peter Hibbs has a nice Calendar demo which uses the "C" approach, IIRC. Not sure if there's something similar in the code archive here (one of the more-regulars may know).
If we had the equivalent of a WPF StackPanel, this would be simple! In any case, none of these really fall into beginner categories: it's either non-seasoned expert mode ("oh cool, a new challenge") or seasoned expert mode ("wtf, do I really have to waste time with this bs? <muttering about bad clients and ridiculous requests>")
Edit: I suppose also you could embed a web-browser control and use a local html with masonry-style JS library to lay out some components to give the effect of a stackpanel and use the browser control DOM API to pass the data into the local document and render via JS, but that's really stretching the bounds of practicality pretty far (feasible, yes, but not practical except at great need)...