Assuming you are refering to gramaphone records as opposed to records in a
Quote:
table, the normal way of doing it is to have a table of rRecords, a table of
Categories abd a JoinRecordCategory table consisting of RecordID and
CategoryID as joint keys.
>
You then have a Record form and a continuous subform based on the
JoinRecordCategory table and linked to the main form on the RecordID
>
The subform has on it a combo box for selecting the category and the
ControlSource will be JoinRecordCategory!CategoryID
Thanks for your reply, Phil. I'm sorry it's taken so long to get back
to you.
It's not a gramophone database, that's my fault for using archaic terms
such as "files", "fields" and "records" when I should be using
"tables", "columns" and "rows". It just shows you how far out of touch
I've got!
Anyway, it's not a bad analogy so I'll stick with it. Let's say I have
categories of "Rock", "Punk", "Pop" etc. On frmRecords I want a
continuous subform of categories where all of them are displayed as
text, and only the relevant ones are checked (so a song can be both
"Pop" and "Rock" for example). Where a category is added _after_ the
song, the triplestate of the checkbox is enabled so that it's plain to
see where songs need attention because new categories may apply.
I think I'll have to do it by populating the xref table with all
current categories when the song is added, then deal with the absence
of a category at a later stage.
If it sounds a bit ridiculous, it's because it's actually a FAQ
database, and we certainly will be adding categories as the business
moves into new areas, but some existing FAQs may well apply to new
categories. I'd like an easy way of seeing which FAQs predate the new
categories.