I
ISD
Question: How can I institute this naming schema?
Scenario: I have a database with 5 tables. Records in
Table 1 are identifiable by English letters (unlikely that
there will ever be any more than 26 records). Table 2 is
linked to Table 1 and its records are identifiable by the
letter ID from table one plus another character(so,
records in Table 2 have ID like AA, AB, AC, BA, BB, BC and
so on where the first letter identifies the linked record
in Table 1). This building of id's occurs throughout so
that records in the 5th table have id's such as DCAAB.
I don't think it makes sense to have five linked fields
(even if that's possible) as the primary key for the last
table and in any case, I need to be able to ientify
records by the full letter designation (not D and C but
DC, ie, concatenated). I understand that ACCESS prefers
numbers for indexing and naming and so I am fine with
using an autonumber as primary key. Even so, I would
still like to provide the user with a means to access the
records via the letter designation.
Scenario: I have a database with 5 tables. Records in
Table 1 are identifiable by English letters (unlikely that
there will ever be any more than 26 records). Table 2 is
linked to Table 1 and its records are identifiable by the
letter ID from table one plus another character(so,
records in Table 2 have ID like AA, AB, AC, BA, BB, BC and
so on where the first letter identifies the linked record
in Table 1). This building of id's occurs throughout so
that records in the 5th table have id's such as DCAAB.
I don't think it makes sense to have five linked fields
(even if that's possible) as the primary key for the last
table and in any case, I need to be able to ientify
records by the full letter designation (not D and C but
DC, ie, concatenated). I understand that ACCESS prefers
numbers for indexing and naming and so I am fine with
using an autonumber as primary key. Even so, I would
still like to provide the user with a means to access the
records via the letter designation.