manipulating arrays question

Interesting approach jefman, but all I got was "(0,0)" on report.

I've tried a bunch of different variations of the code and I can't get anything but zeros to report. The only way I've been successfully able to creat an array of the measured tolerance values and report them is by typing in all the LOC#'s manually into the array, like this ASSIGN/ V1 = ARRAY(LOC1.T.MEAS, LOC2.T.MEAS, etc....), then sort up and report min as v1.1 and max as v1.(# of last hit). Which I never am going to take the time to set up something like that because it negates the convenience of getting the two values i want from the array. 99% of the time when I'm inspecting graphite electrodes I just need to know if they're in-tolerance, so max and min tolerance numbers are what I want, and when reviewing 150 (or more) individual points' tol values there's a greater chance an "oopsie" will slip through and down the line (where it becomes a BIG, exponentially more costly oopsie).

I have been trying different ways of getting those "LOC#.T.MEAS" values to generate in an array with looping but with no success yet. I AM going to figure this out one day....then I'll be a demon-slayer.

Interesting approach jefman, but all I got was "(0,0)" on report.

I've tried a bunch of different variations of the code and I can't get anything but zeros to report. The only way I've been successfully able to creat an array of the measured tolerance values and report them is by typing in all the LOC#'s manually into the array, like this ASSIGN/ V1 = ARRAY(LOC1.T.MEAS, LOC2.T.MEAS, etc....), then sort up and report min as v1.1 and max as v1.(# of last hit). Which I never am going to take the time to set up something like that because it negates the convenience of getting the two values i want from the array. 99% of the time when I'm inspecting graphite electrodes I just need to know if they're in-tolerance, so max and min tolerance numbers are what I want, and when reviewing 150 (or more) individual points' tol values there's a greater chance an "oopsie" will slip through and down the line (where it becomes a BIG, exponentially more costly oopsie).

I have been trying different ways of getting those "LOC#.T.MEAS" values to generate in an array with looping but with no success yet. I AM going to figure this out one day....then I'll be a demon-slayer.