ZackJones

The majority of mine are released with the chain that came with the tags. I do shorten the chain though. I don't see any real need for having an extra long chain, especially for small travel bugs.

Thanks for the replies so far. One of the goals I had for the coin was to try and create one that I could sell for $5.00. I don't see that happening, especially if it is going to be trackable which is a must have, IMO.

fishDog: Good luck on your trip. Let us know how things went when you get back.

I'm thinking about having a coin made and I want to make one that sells well since I don't have a ton of money that I want to tie up in this project . With that in mind is there a generally accepted diameter and thickness of a coin? Not that it matters but I'll state this anyway - I'm not trying this to make money, but if I happen to make any money off of it I would donate any extra money to BikeDog's memorial fund. Given options of 1" (25mm) 1.5" (38mm) 1 5/8" (42mm) 1.75" (45mm) 2.0" (50mm) for diameter and options of 2 mm 2.5 mm 3.0 mm 3.5 mm 4.0 mm 4.5 mm for thickness what do you prefer? The cheapest price for a coin would be 1 inch diameter and 2 mm thickness but is that too small or too thin?

I just checked up on some of my TBs and right now the longest any of them have sat idle is 6 months. I posted a note on one cache page and emailed the cache owner on another asking them to check on the TBs the next time someone visits the cache or when the owner performs maintenance. I also emailed 3 individuals that have been holding TBs for extended durations. If they reply saying the TB is gone I'll just grab it and re-release using the copy tag.

2 for me as well. I think the uniqueness of the coin makes it worth $8.00 to me.

We have a brand new Wally World opening just down the road tomorrow. I'm going to go there and see if they have any white jeeps.

I found this link in our state-wide forum and thought I'd share it here. Geocaching Article

Dupe post deleted. Server puked.

don't send emails to contact@Groundspeak.com that's a black hole, it seems. Send it to contact@geocaching.com and you should get a tracking number for your email along with a nice reply from Michael a short while later. At least that has been my experience.

As an outsider looking in here's some things that pop into mind for you guys to consider (you may be doing some of these things already). 1 - Store connection string in web.config and use it for every connection. Even the slightest difference in the connection string info causes a new connection to be created instead of using a cached connection. 2 - Use datareaders where possible instead of datasets. 3 - Use SQLHelper class library for data access. This allows you get a data reader with a single line of code instead of created Connection and Command objects. 4 - If you're using Connection and Command objects are you opening as late as possible in the code and closing as soon as possible? Do you include the close connection option when executing data readers? 5 - All database access must go through stored procedures. 6 - Use transactions. I know they are more expensive in terms of processing but it would eliminate all of the multiple logs to drop travel bugs and multiple logs to retrieve them. 7 - Migrate to ASP.Net 2.0 and use asynchronous pages. (This is something I'm looking into now for our projects). I'd be happy to help in anyway I can. I'll sign an NDA if you want.

My first find ever was in Bermuda. In the USA I've found caches in CO, TX, AL, GA, FL, NC, SC, MD and AK

Well I am a programmer and I do develop high-traffic web sites, which really doesn't mean squat . I would be happy to assist in any way that you an Raine could use any help with improving the performance of the web site. I know you want developers in your offices but you could shoot out code to developers for peer reviews so we could make suggestions based upon how we develop our web sites.

Ramness570: What, if anything, happens when you click the recalc button?

Thanks for the post. Downloading now

You have to create what is called a hyperlink in the description for the travel bug. If you'll post the names of the two TB's you want to link together I'll take a look at 'em and send you the exact text to insert as the hyperlink. I could try to explain it but it would take way less time to just send you the code to insert

I'm a cache dumper too. I dump everything out and then look for what could make a good travel bug. I'm sure I've passed up some good swag doing this but I've also found lots of different things that shouldn't be in the cache which I CITO (working lighters, knives, etc).

As a courtesy contact the TB owner and make sure he/she is agreeable with you mailing the TB. Some folks don't like their TBs being mailed.

Have FloridaCacher go to the coin page and click on the recalculate mileage button to see if that gets the mileage updated.

2 coins for me.

I wouldn't wait. They will get it fixed eventually. Besides if you wait you'll have to go back and log old finds or start it logging your miles at a later date.

I got mine as well and will start placing them tomorrow.

There are also issues between the Search Page (go to page 3 and look at Zack's Traveling Coin) mileage there shows 16557. On the Zack's Traveling Coin page the mileage shows as 16530.6

funinthealps: Sorry for your loss . Just because an event wouldn't be approved there are other things you could do such as: 1 - release a travel bug in your cousin's memory. You could use the travel bug to tell about the CFF. I have seen travel bugs for diabetes and the Lance Armstrong Foundation and I've released a breast cancer travel bug in honor of my mom who's a cancer survivor. 2 - Place a cache that serves as a memorial to your cousin. You could describe CFF in the cache description and if folks feel motivated to donate they will.

I recently adopted a cache that's a little ways away from my home. Shortly after I adopted it a cacher local to the cache contacted me and said they were local to the cache and would check on it from time to time if I wanted them to. Perhaps something like that would work out in this situation. Look at the owner's profile to see they last logged into the website. If it's been a long time they're probably no longer interested in maintaining it.