Numbering Parts That We Run Over and Over

[[Ky...]]

We have parts that we run over and over. My concern is when we save the points for later use if we need them. My concern is if I start at #1 each time will I overwrite the pervious #1's. Am I just worrying about nothing or am I screwing up?

[[Ch...]]

I add the date and time(down to the second) to prevent my measuring points files from over writing.

[[Ow...]]

Maybe?
I always save them with dates like 4.7.20-1.
That way if you run them tomorrow they'd be saved as 4.8.20-1

[[Ow...]]

See

[[Ky...]]

Thanks All for your ideas. We are going to try both and see which idea works for us. I was loading points and saw that I was missing #1 and #2. We have the reports but that just doesn't help sometimes.

Next question, how do you handle the program if you add things later on or figure out a better way of running the part after reading something from the Board. Do you obsolete the old program so you don't screw up all the previous point data or what. I have changed somethings in a program then I loaded points and it wanted to rerun some things on a part I didn't have any more. I needed to think about these things years ago. More things to worry about 😮

Thanks for the help and any ideas about the questions above.
Kyle

[[Ke...]]

As far as making changes to the program you can do several things erase old Characteristics, Mask them, Group them label them something like "Old Characteristics" then mask the whole group. Grouping/keeping them lets you review them later to see your programming progression.
Re-Run
You can load old points, rename the report and then run "Subsequent Evaluation" then I believe this should keep the original Measuring Points intact.

[[Ky...]]

Thanks I didn't think about grouping the old and the new. That will make things easier
Thanks All
Kyle