C
Clif McIrvin
I've noted with interest various threads dealing with the question of
incrementing values, and have noticed that there seems to be a common
reaction along the lines of, "That's a calculated value, and shouldn't
be stored."
In my application under development one of the requirements is to handle
scheduled piece-work (or custom) production. It is quite common for a
job to have a series of pieces identified by the JobID and an
incrementing suffix.
When entering new jobs, it is quite convenient to enter the common
information for each piece once and simply duplicate that record while
incrementing the suffix for each successive piece.
From when I began getting acquainted with Access (and RDB concepts)
until now I have learned a lot, and have seen how to restructure my
production data design from 'wide' to 'tall' using child tables for a
variety of data that may (or may not!) become related to a piece during
it's production cycle -- but I have not seen any other way to handle the
production records themselves - that is many individual records nearly
identical except for the ID suffix, production date and various related
child records.
The (simplified) structure I am contemplating looks something like this:
Jobs table
JobKey, autonumber, PK
JobID, Human assigned, Text, Indexed, Duplicates Allowed (I don't like
that part, but without major changes to the way internal company systems
work that isn't going to change any time soon.)
JobName
(etc)
Production table
PrdKey, autonumber, PK
JobID, FK
Piece, Text (incrementing suffix described above)
JobID + Piece, Index, Duplicates Allowed
Date Produced
Date Promised
(etc)
PrdRemarks table
RemID, autonumber, PK
PrdKey, FK
Remark, Text
RemDate, Date
QCInfo table
QCID, autonumber, PK
PrdKey, FK
QCDate, Date of inspection
QCStatus
(etc)
Anyone have comments or suggestions for me?
incrementing values, and have noticed that there seems to be a common
reaction along the lines of, "That's a calculated value, and shouldn't
be stored."
In my application under development one of the requirements is to handle
scheduled piece-work (or custom) production. It is quite common for a
job to have a series of pieces identified by the JobID and an
incrementing suffix.
When entering new jobs, it is quite convenient to enter the common
information for each piece once and simply duplicate that record while
incrementing the suffix for each successive piece.
From when I began getting acquainted with Access (and RDB concepts)
until now I have learned a lot, and have seen how to restructure my
production data design from 'wide' to 'tall' using child tables for a
variety of data that may (or may not!) become related to a piece during
it's production cycle -- but I have not seen any other way to handle the
production records themselves - that is many individual records nearly
identical except for the ID suffix, production date and various related
child records.
The (simplified) structure I am contemplating looks something like this:
Jobs table
JobKey, autonumber, PK
JobID, Human assigned, Text, Indexed, Duplicates Allowed (I don't like
that part, but without major changes to the way internal company systems
work that isn't going to change any time soon.)
JobName
(etc)
Production table
PrdKey, autonumber, PK
JobID, FK
Piece, Text (incrementing suffix described above)
JobID + Piece, Index, Duplicates Allowed
Date Produced
Date Promised
(etc)
PrdRemarks table
RemID, autonumber, PK
PrdKey, FK
Remark, Text
RemDate, Date
QCInfo table
QCID, autonumber, PK
PrdKey, FK
QCDate, Date of inspection
QCStatus
(etc)
Anyone have comments or suggestions for me?