About the only way to solve this problem is not placing a Travel Bug in a cache unless you know that you can get to a computer to log it within a reasonable time.
However, I particularly like putting travel bugs in caches far away from my home, when I have a chance to travel - for example, I like putting travel bugs that I find in Arizona in caches in Utah when I travel to Utah during the summer. However, when I am traveling to Utah, I camp in my SUV and don't have access to a computer until I get home.
There is a solution to the problem of finding a travel bug in a cache that has not been logged in that cache. First, "grab" the travel bug, then put the travel bug in the cache that you found it in, then remove it from the cache. For example, after a game at Bank One Ballpark this summer, I found a travel bug in the G-O BOB cache at Bank One Ballpark. When I got home, I went to my computer to log the travel bug finding, but it hadn't been logged in the cache yet.
The person who put the travel bug in the cache had put it in there earlier same day, and they hadn't yet gotten to a computer to log it in when I signed onto Geocaching.com. Therefore, I "grabbed" the travel bug, then put it in G-O BOB, and then removed it from G-O BOB. This correctly placed the travel bug in the G-O BOB cache and then put it in my hands. I moved the travel bug to another cache in South Mountain Park three days later.
Ken
(text/plain)