Yes, order of record creation is irrelevant.
A revision 3 upgrade can be done before 1 and 2? Guess I am in a software upgrade mindset.
Yes, order of record creation is irrelevant.
A revision 3 upgrade can be done before 1 and 2? Guess I am in a software upgrade mindset.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
It's a physical product that has been designed.
Let's say for example that it is an engine and changes to the design are made as such:
Date: 01/09/2015, Revision 1: Metal plate added bottom left of engine
Date: 02/09/2015, Revision 2: Smaller piping used on top of engine
Date: 03/09/2015, Revision 3: Filter style changed
Products from revision 0 (or the original ones) may have the filters changed first (revision 3), but will still need to have the other fixes/upgrades applied (revisions 1 and 2) at some point, and we need to track this (and we need to make sure that all products that we have produced eventually are fixed/upgraded to the current revision)
Unfortunately it's not like software =(
I don't see why the normalized structure I suggest can't accomplish that. Should be able to design queries to identify which customer-placed products have not received what upgrades.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.