If I just log the caches that I had found previously it's going to abnormally through off the stats... I know this might annoy *someone*. :-) :-) -----Original Message----- From: Loran Wilcox [mailto:loranwilcox@chartermi.net] Sent: Mon 6/2/2003 6:21 PM To: listserv@azgeocaching.com Cc: Subject: Re: [Az-Geocaching] Kangaroo's revenge Create a new account and enter logs for those caches that you have already found. Use the original find date and just put a note in your online logs that you previously logged them as part TeamLeapLab. If any cache owner doesn't except that then just refind them and make a physical log entry. It's not like you didn't find the cache. Team Sand Dollar ----- Original Message ----- From: Mike Ingoglia To: listserv@azgeocaching.com Sent: Monday, June 02, 2003 8:07 PM Subject: [Az-Geocaching] Kangaroo's revenge I have a question? Brian is no longer employed at the company which inspired the name "TeamLeapLab" and decided to change the team name to Team AZevil. I guess he had the right to do this as officially he was captain since he was the one that went through the motions of signing up... although I was the one that first suggested we start geocaching as he had never heard of it before (no, I'm not bitter). :-) Originally I thought he was starting a new team until I just tried to log into "our" account and noticed it no longer existed and that all "our" past finds are now under Team AZevil instead of TeamLeapLab. I originally noticed this after wondering why I hadn't received any more finds on our trademark "The Kangaroo is Watching" cache.... Well, it had been archived... that's why. My question is this. . . if I decide to start a new team can I in good conscience revisit all of the caches I did under what is now considered Team AZevil and log them as a new find? After all, I was with Brian at all but a few of those caches... we were always a two cacher team with the exception to a handful of caches he did with his wife. Mike Team (crap, I guess I don't have a home). PS... I guess the travel bug that I released will never find it's way home. :-(