DaxVolks

Thank you, HHL, for the response.

After some additional experimenting, I discovered it works on some events; not others. This did not work: GC9G9BW This did: GC9D6AE

Just tried to export an event's data to my Outlook calendar and received this error message: Any suggestions would be appreciated. This page isn’t working right now www.geocaching.com sent an invalid response. ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION

http://www.geocaching.com/my/logs.aspx?s=1&lt=3 Will give you a list of your DNF logs. See....I knew there was something I'd used before but forgotten...and a kind person here would give me that whack to jog those memory cells back into place. I'm beholden to you!

So OCD I'm browsing gc.com and the forums to figure out a way to generate a list of all my log entries ever to build that go-look-again list. (You know, I might have overlooked putting one on the watchlist!)

Hi! Any chance you still have a "Flip a Friend" coin? If not, any ideas where I might find one? Thanks for your help. Barb the DaxiMutti of the DaxVolks

Thanks, everyone for your suggestions. Just to clarify...we've been caching paperless since 2004, compliments of the Garmin iQue. We do print just the map if we feel the need to take that along on the hunt. But, as someone else said above, it's nice to just print a complete cache page now and again...for whatever reason. Several of my local friends are having the same issue of the second map overwriting the first several lines of the logs. It seems like a website issue rather than a local printer/browser issue. Thanks again for all your feedback.

Is anyone having trouble with the second map on the cache page becoming huge when printing the cache page? Have not changed anything with my browser, OS, printer. That second map will print in normal size on the second page, then print again in a huge format on the third page, blocking out the first one or two log entries.

Thanks for the quick response!

When looking for public routes (no matter the search mechanism used) I can view only the first page of routes. If I select "next page" or the next page's number, I get either a blank page or a page with what appear to be random routes. I reviewed a few other threads in the forum, but found no resolution to the problem. I created several routes, marked them public, and asked a fellow cacher to use them to create a PQ. She could not access those routes. The only way I can access them is under "your created routes." Any help would be appreciated.

Thanks for the quick fix.

Count us in as well. We pay annually and just renewed in October. We have no GSAK issues - no scripts, no stats, etc. Totally unsatisfactory. I notice we're all showing as Premium Member Group in the Forum. Not sure how we got labeled as tadpole, but that's ok, I guess.

We ran several day before yesterday and they worked just fine. When we tried yesterday we got the same error message. Our basic PQs ran without a hitch. Sigh.

Not for a long time now, but we did. We would usually print the first page or two of the cache page and put those on a clipboard. That way we had the description and hint (and probably the last log or two). The clipboard became very cumbersome, so we'd just staple or clip the pages together and fold them. Much easier to stuff in a pocket or fanny pack. If we were going after just a few caches, we'd jot the notes down on an Excel form we created and just take that one or two sheets along. That was the best solution for us until we abandoned the paper all together. We did find, however, that when we made notes, we'd invariably forget to jot down something important on at least one of the caches. We would be happy to email you a copy of the spreadsheet form if you desire.

#%!#*!!! Hey, wait.....nothing's ever as bad (or as good) as first reported! We got in on this way late. Guess like many of the commenters, we tried to do a PQ today and found our "get eBook" option missing. We've been using Mobi on our iQue for quite some time and while it's a little cumbersome, we love not schlepping paper around. After reading through most of the posts, we dashed off our $8 and loaded CacheMate. Wow. We'll not be going back to Mobi any time soon. Thanks to all who are offering solutions. It made what started out as a really bad caching day, just another normal, fun experience.