Quantcast
Channel: GSAK Forum
Viewing all articles
Browse latest Browse all 75657

enforcing unique CacheID numbers by clyde - 2013-07-01

$
0
0
QUOTE (hynr @ July 01, 2013 02:46 pm)
While all the values that show up are all numeric, I note that it is a string variable and sorts like a string rather than a number. I also note that I can type in characters other than numeric.

Yes, this is deliberate. Although Groundspeak Cache ID's are numeric not all sources of cache data are.

QUOTE
Do we know that non-numeric info will work OK in the Garmin GPRs?

Personally I don't know. Now that we are forcing the ID to be unique (and when we do this we always generate a unique number) I would think that in the majority of case there would be no need to change this number. However, if you *are* going to fiddle with this data then the onus is on you to know the consequences.

BTW, if you really want that column to sort strictly numeric then you can run the following macro code:

GSK
SqlSort OrderBy=CacheId + 0

Viewing all articles
Browse latest Browse all 75657

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>