G
Guest
I'm putting together a small database to keep track of process flow diagrams.
Each diagram has a unique diagram "number", e.g.
R-15100-500-O
The R-15100-500 is the number and the -O bit is the revision; O for original
and then A, B, C etc as the diagram evolves.
I need to store a record of all revisions for a given diagram and I enter
this through a simple form that has a control for the number and a drop-down
combo for the revision.
What I want to prevent is the same, combined, number being used. i.e I can
have many diagrams R-15100-500 but only one with the unique suffix -O, -A etc.
I can join these two together on the form and have toyed with how to get
that, now unique, identifier back to a field in my table but posts I have
read point out that this is not good practice.
I could change the way I enter the identifier and get rid of the drop down
revision box but it would be easier for my users to leave as is.
Has anyone any pointers? Appreciate any help.
Andy
Each diagram has a unique diagram "number", e.g.
R-15100-500-O
The R-15100-500 is the number and the -O bit is the revision; O for original
and then A, B, C etc as the diagram evolves.
I need to store a record of all revisions for a given diagram and I enter
this through a simple form that has a control for the number and a drop-down
combo for the revision.
What I want to prevent is the same, combined, number being used. i.e I can
have many diagrams R-15100-500 but only one with the unique suffix -O, -A etc.
I can join these two together on the form and have toyed with how to get
that, now unique, identifier back to a field in my table but posts I have
read point out that this is not good practice.
I could change the way I enter the identifier and get rid of the drop down
revision box but it would be easier for my users to leave as is.
Has anyone any pointers? Appreciate any help.
Andy