| QUOTE (Kai Team @ August 11, 2013 07:27 am) |
| I just realized that the easiest fix for this is to convert your FindNum field from String to Integer - no macro required, and it should take care of any future additions regardless of how they are formatted. The only downside I see to this approach is that if the FindNum field is empty for a cache, it will show a zero (0) instead of being blank (i.e. it's just cosmetic). 1) Back up your databases and settings so that you can reverse the process if the results are not to your liking. 2) Go to Waypoint>Custom Data>Fields, select FindNum, click "Edit". 3) Choose "Integer" in the "Type" drop down. 4) Click "OK", "Save", and "Save" to exit the dialogs. GSAK will remove all spaces from all Find Numbers, will display them right justified, and will sort them in numerical order when you click the column heading.  |
Thank you for the quick reply and fix. This seems to have done the trick. From what you said above I was wondering do I need to make a small mode to Fillfinds.gsk to allow for finds greater than 9999? I was looking at the code and I am not sure what would need to be changed but I did notice this line of code and it seems to have to do with the size of the string:
| CODE |
$d_UserData=Str($Sequence,5,0) |
Would I increase the number 5 to something larger?
Again thank you for your help and fix.
