Serialization restarts at #1 for each lot and I am intending on entering the job number (which seperates the lots) to give it the seperation, Will this work? I F'in hope so. (Monday ugh)
Yes, sort of.
When using a tracefield to sort data, you MUST create a QUERY (in Dpeditor) for each tracefield and tracefield value. So, yes, you can do it. You can create the query at any time and you can add them later.
So, you will have a tracefield "JOB_NUMBER" and a value, lets say 12345 (for job #12345). You run the parts. You make a QUERY called 12345, select the TRACE NAME of JOB_NUMBER set the OPERATOR to "=" and enter the trace value (12345). Now, no matter WHAT data "part" the info is stored under, you select QUERY 12345 and it will ONLY show the data for JOB_NUMBER 12345 (tracefield) that has been saved.
Did ya follow that?
Then, anytime you add a new JOB_NUMBER, you add a new query for it and BINGO!, Bob's yer Uncle.
Serialization restarts at #1 for each lot and I am intending on entering the job number (which seperates the lots) to give it the seperation, Will this work? I F'in hope so. (Monday ugh)
Yes, sort of.
When using a tracefield to sort data, you MUST create a QUERY (in Dpeditor) for each tracefield and tracefield value. So, yes, you can do it. You can create the query at any time and you can add them later.
So, you will have a tracefield "JOB_NUMBER" and a value, lets say 12345 (for job #12345). You run the parts. You make a QUERY called 12345, select the TRACE NAME of JOB_NUMBER set the OPERATOR to "=" and enter the trace value (12345). Now, no matter WHAT data "part" the info is stored under, you select QUERY 12345 and it will ONLY show the data for JOB_NUMBER 12345 (tracefield) that has been saved.
Did ya follow that?
Then, anytime you add a new JOB_NUMBER, you add a new query for it and BINGO!, Bob's yer Uncle.
