Sorting with DISTINCT

[lodmark]

Cascading combo boxes would solve my problem.
But as it works today when I only select the artists from the artist table and with a connection to record_ID sorted by release year, I get all the records that that artist has released and that I have in my collection one after the other when I scroll with the form's arrows.
I think it's pretty neat.
@Pat Hartman
I think my tables work and that with enforced RI. That is, the most important tables such as artist, record (album) and music (Song).
I know that I don't have a good grasp of genre or media, it doesn't seem to be included in all forms or is different as you point out.
This needs to be solved.
But next week I'll look at cascading combo boxes, I think.
Have a nice weekend everyone.

 

[Pat Hartman]

I think my tables work and that with enforced RI.

I think I can drive on the highway blindfolded. We're both wrong. What's a little bad data here and there? No big deal. This is a hobby project for you so having bad data isn't going to cause you to make bad business decisions so do whatever you want.

 

[Ken Sheridan]

But next week I'll look at cascading combo boxes, I think.

You might find the attached little demo file useful. Note that where data is in a tree structured hierarchy, only the lowest level in the hierarchy should be stored in a referencing table, city in the demo. Otherwise redundancy is introduced and the table is not normalized to Third Normal Form (3NF), leaving the table open to update anomalies. The values in the upper levels should be returned in unbound controls, as illustrated in the demo.