| QUOTE (Kai Team @ August 10, 2013 05:38 pm) |
| FillFinds pads with spaces to insure proper sorting in string (text) fields for up to five digits (99,999 finds). It looks like you are getting close to the limit of four digits (9999)! Image may be NSFW. Clik here to view.  I can't tell from your screen shot what column "FindN..." is and whether it is a string or numeric field. Did you rename an existing GSAK field (User Data or User Sort)? Or is this a custom field? If you tell me what the exact database name of the field (i.e. the original column name if you've renamed it), and, if it is a custom field, what the properties of the field are (Waypoint>Custom Data, Fields, Type column) I can write a macro to go through and add or remove spaces, as needed. |
Thank you for the reply. The FindNum field is a custom field. Here is a screenshot of how I set it up:
Image may be NSFW.
Clik here to view.
I took your code and created the macro to place the FindNum into this field each time I log a cache with Publish Logs. Since I had so many caches that I had found I had to move Find Numbers from the User Data field into this new column since I had not been using this method over the years and this is why some of the numbers have a leading space while others do not. This of couse caused sort problems. I also have used the Fillfinds macro some lately due to the API problems and not being able to use Publish Logs.
This is the code I use to create the FindNum:
| CODE |
IF Seek($_PublishCode) $Found = sqlite("sql","select g_FoundLog(Ltype) from LogsAll where rowid = $_PublishId2","") IF $Found = "1" $Count=PublishTags("%count") $Update=CustomPut("FindNum",$Count) # $Update=CustomPut("UserData",$Count) ENDIF ENDIF |
