BBosman

One of each metal for me as well, please.

This has got to be the best alternative suggestion that has been made. One which I was not aware of. Unlike the cache stats that searches by words, your macro searches by what I want it to search by. My problem is that I use GSAK, but I keep it simple. I really don't know how to run such a filter. Any chance you can post a step by step idiots guide for me? 1. Save the code below into a textfile called ftf.txt somewhere on your harddisk. 2. In GSAK go to the menu item Macro and select Run. 3. Use the small folder icon left of the Macro File box to browse to the saved ftf.txt from step 1. 4. Klik OK. 5. You get a list of all caches in your current view that you found within 7 days of being published. MacroFlag Type=Clear Range=All Goto Position=Top While not ($_eol) If $d_Found = True If $d_FoundByMeDate <= $d_PlacedDate + 7 $d_MacroFlag = True EndIf EndIf Table Active=caches Goto position=Next EndWhile Mfilter If=$d_MacroFlag There are some things to take note of: 1. It doesn't take changed Placed Dates into account. 2. It doesn't include caches where the FTF was more than 7 days after publishing. 3. It works on my GSAK. That's as far as the support goes. 4. If you want to tweak the 7 days, just change the $d_PlacedDate + 7 part.

Don't forget that a country as for instance Germany has 29000+ caches. That's a BIG pocket query. Not taking the effect of mail size limits into account, this would consume a lot of bandwith. And even if you have one. How would you keep it up to date (new/changed/disabled/archived caches), if you can have only one a year?

For "small" countries a pocket query with all caches would be managable. But Gemany for instance has 29000+ caches. That's one BIG pocket query.

Create one "nearest query", with caches placed before a certain date and one "nearest query" with all caches after that date. You'll have to experiment which date gives you around 500 results for the first query. And if you also exclude found caches your query range will expand over time due to found and/or archived caches. This should give you almost the same result as the 1 1000 caches query.

Put me down for 1 set as well.