Quote:
|
Originally Posted by sjk
Code:
NAME PDATE SP RATING
ABRAN PASO 2/21/2016 -4.37635689419911
ABRAN PASO 1/31/2016 25.2828596536973
ABRAN PASO 1/16/2016 41.8820448577677
ABRAN PASO 2/22/2015 19.9778323135338
ABRAN PASO 10/27/2014 38.0443862398989
ACCELERATO 6/16/2016 39.9416428655098
ACCELERATO 5/30/2016 31.7067170449216
ACTION AMOUR 6/2/2016 34.4451868100831
ACTION AMOUR 3/29/2015 20.6270253522822
ACTION AMOUR 1/16/2015 24.6326183224922
AFTER THE GOLDRUSH 5/29/2016 34.3078001232938
AFTER THE GOLDRUSH 5/6/2016 41.9937828020845
AFTER THE GOLDRUSH 4/9/2016 23.5772453411666
AFTER THE GOLDRUSH 3/19/2016 54.8028873107904
AFTER THE GOLDRUSH 1/10/2016 56.0233139527162
ALBANO 5/21/2016 90.8337854918294
ALBANO 8/30/2015 101.945145362918
ALBANO 8/1/2015 85.8306008801825
ALBANO 5/30/2015 77.6737642485744
ALBANO 3/28/2015 101.994671418633
Code:
ctr NAME PDATE SP RATING
918 ABRAN PASO 1/16/2016 41.8820448577677
919 ABRAN PASO 10/27/2014 38.0443862398989
920 ABRAN PASO 1/31/2016 25.2828596536973
921 ABRAN PASO 2/22/2015 19.9778323135338
922 ABRAN PASO 2/21/2016 -4.37635689419911
923 ACCELERATO 6/16/2016 39.9416428655098
924 ACCELERATO 5/30/2016 31.7067170449216
925 ACTION AMOUR 6/2/2016 34.4451868100831
926 ACTION AMOUR 1/16/2015 24.6326183224922
927 ACTION AMOUR 3/29/2015 20.6270253522822
928 AFTER THE GOLDRUSH 1/10/2016 56.0233139527162
929 AFTER THE GOLDRUSH 3/19/2016 54.8028873107904
930 AFTER THE GOLDRUSH 5/6/2016 41.9937828020845
931 AFTER THE GOLDRUSH 5/29/2016 34.3078001232938
932 AFTER THE GOLDRUSH 4/9/2016 23.5772453411666
933 ALBANO 3/28/2015 101.994671418633
934 ALBANO 8/30/2015 101.945145362918
935 ALBANO 5/21/2016 90.8337854918294
936 ALBANO 8/1/2015 85.8306008801825
937 ALBANO 5/30/2015 77.6737642485744
Code:
NAME MaxOfctr
ABRAN PASO 922
ACCELERATO 924
ACTION AMOUR 927
AFTER THE GOLDRUSH 932
ALBANO 937
Code:
MaxOfctr NAME PDATE SP RATING
ABRAN PASO 1/31/2016 25.2828596536973
ABRAN PASO 1/16/2016 41.8820448577677
ABRAN PASO 2/22/2015 19.9778323135338
ABRAN PASO 10/27/2014 38.0443862398989
ACCELERATO 6/16/2016 39.9416428655098
ACTION AMOUR 6/2/2016 34.4451868100831
ACTION AMOUR 1/16/2015 24.6326183224922
AFTER THE GOLDRUSH 5/29/2016 34.3078001232938
AFTER THE GOLDRUSH 5/6/2016 41.9937828020845
AFTER THE GOLDRUSH 3/19/2016 54.8028873107904
AFTER THE GOLDRUSH 1/10/2016 56.0233139527162
ALBANO 5/21/2016 90.8337854918294
ALBANO 8/30/2015 101.945145362918
ALBANO 8/1/2015 85.8306008801825
ALBANO 3/28/2015 101.994671418633
It took 5-10 minutes to write a few queries to do what I suggested and I could put those in a macro that would perform all the actions in a few seconds any day I wanted to.
I have dozens of tables that are recalculated each day and that I have not looked at in 15 years. They always calculate correctly. |
This is what has happened to me in the past.
I'd create a table with an autonumber field that had all the data sorted correctly. My process would work fine. Somewhere along the line I'd go into that table and resort the data manually to do some research. When I'd exit, I'd accidentally save it. Next time the process ran it would create the next set of records in the new (and incorrect) sort sequence and the autonumber field would be screwed up. Then I'd have to regenerate the whole thing the correct way. Naturally, that's my fault for being careless. But I move in and out of tables manually all the time looking things up and sometimes forget to not save it if the sort sequence is critical.
I was able to create the table the way you suggested the other night very quickly. I'm sure it will work fine when I'm done developing all the queries in the sequence....until I screw up the sort again.
I probably should just put a sort into the sequence of queries to make sure it's always right before I add any new records.
