Hi Steve - thanks for taking the time to help out!
As I continue to experiment, it should be that I don't need
to go this route. However, if it is managable, I can see
this being advantageous in many cases. So, if you have any
ideas as to the feasibility of this, I'm all ears. Here is
(hopefully) a better explanation:
We have a database of 11000+ records (musical chants - I
won't bore you..), each of which is found in any number of
manuscripts (up to 80+) - could be found in only 1, or
could be in 20 or more. This perhaps explains a
not-too-clever or efficient table design.
ID MS1 MS2 MS3 MS4.....to MS80+
15 a
16 b
17 a c
18 d
Certainly I welcome any suggestions as to the design of the
table, provided this can be done automatically via a query
or other method (due to the size and nature of the data).
Originally (as per my original query), I was wishing to get
the following results:
ID MS
15 MS1
16 MS2
17 MS1
17 MS3
19 MS4
where I could get the FieldName (names of the manuscripts,
here denoted by MS1, MS2, etc..) returned as data.
As I've been thinking this through, I think I can get the
results I want if I can construct a query that will
generate the following results instead (from data above):
ID MS
1 a
2 b
3 a
3 c
4 d
etc..
From this, I should be able to do what I need. Now (please
excuse my access-newbieness) I'm trying to figure out how
to do this - I'm sure this should be easy, and I've
probably even done it in the past, and yet, well,... here I
am asking you experts.
Hope this helps to clarify - and many thanks for your time!
Martin Lacoste