Recent content by OwenW

I hope the bridge game went well! It has been years since I played, but I still hold it to be the greatest game ever invented. Thank you for clearing that up. I hadn't realised that there was such a distinction between having combo boxes on the tables (which then naturally transfer to the...

In this example, that is deliberate, because people can serve in shifts within more than one division. I shall look up cascading combos.

Aha, you use a query! That makes a lot of sense. Would you mind going into more detail about how one does that?

1. I've just been using pgdn to scroll between divisions, because when I tried to insert a multiple items form it wouldn't let me insert another one for some reason. 2. In this instance we don't want to restrict the selectable shifts to divisions, because somebody can be assigned to any...

Thank you for that. You seem to have come up with a similar solution to me. To put my problem in the shape of your example database, each hobby becomes an after school club, and each student and after school club is associated with a specific school. How do you limit the content of the drop down...

I think that the organ thing is causing some confusion, doubtless to my inability to explain thoroughly. I don't think I have misunderstood as fundamentally as you suggest, although I am happy to proved wrong on that. My reason for saying that I needed to match text to text rather than number to...

Yes, but they would be different pipes. In other words, the ranks table is describing physical pipework, rather than nomenclature. In the same way that you may have two Joe Bloggs in your table, you wouldn't combine them because they represent different people. So a Stopped Diapason on one...

Yes, I am sure that this is a bad way of doing it, but as you will have worked out, I don't really know what I'm doing. In order to make the link table work practically I needed to match words against words, rather than numbers against numbers, which could so easily go wrong. Having set it up as...

Yes, indeed. Let us consider Durham Cathedral (attached). A large instrument like this will have divisions, labelled 'Great', 'Swell' and so on. Each division is associated with a particular keyboard on the organ, although they can be moved around through controls called 'couplers'. Within each...

OrganID needs to be in the Ranks tables because each rank can be part of only one organ, and that relationship is important. For example, I would want to design a query to look at the average number of ranks per organ within each calendar year. I put OrganID in the link table purely to attempt...

Forgive me, I am such a novice at this. I am constructing a database to house details of a number of pipe organs, for academic research and not for public use. Although the design of the database itself is relatively simple (although quite complicated enough for me), the number of fields per...