[Az-Geocaching] Help with a TB log
RAND HARDIN
listserv@azgeocaching.com
Tue, 11 May 2004 16:48:30 -0700
------=_NextPart_001_0000_01C43777.CA46F3E0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Just notify "Team RED DOG" that they need to grab it back from you (or yo=
u can place it back into the cache, "No, Mine's The Biggest!..." and have=
"RED DOG" retrieve it again - this way you get the mileage).
There may be other ways to correct this, but without knowing which travel=
bug you're referring to, the above recommendations will help.
Rand
----- Original Message -----
From: SquishyGecko
Sent: Tuesday, May 11, 2004 4:03 PM
To: listserv@azgeocaching.com
Subject: [Az-Geocaching] Help with a TB log
Okay, so yesterday AZcachemeister archived his "Mine's Bigger" cache and
delivered the TBs to GCJCQ0. This morning I went created a log on one of=
my
TBs as "Grabbed it from somewhere else" and just before I wrote a note on
GCJCQ0 to log it as being there, Team Red Dog posted a log that they'd
retrieved it. So I deleted my log entry on the TB, however it still show=
s
as being in my inventory. How on earth do I fix this? My immediate thou=
ght
is to log a note on GCJCQ0 dropping it off, and have Team Red Dog log it =
as
retrieved again. Any thoughts?
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.679 / Virus Database: 441 - Release Date: 5/9/2004
____________________________________________________________
Az-Geocaching mailing list listserv@azgeocaching.com
To edit your setting, subscribe or unsubscribe visit:
http://listserv.azgeocaching.com/mailman/listinfo/az-geocaching
Arizona's Geocaching Resource
http://www.azgeocaching.com
------=_NextPart_001_0000_01C43777.CA46F3E0
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<HTML><BODY STYLE=3D"font:10pt verdana; border:none;"><DIV>Just notify "T=
eam RED DOG" that they need to grab it back from you (or you can place it=
back into the cache, "No, Mine's The Biggest!..." and have "RED DOG" ret=
rieve it again - this way you get the mileage).</DIV> <DIV> </DIV> <=
DIV>There may be other ways to correct this, but without knowing which tr=
avel bug you're referring to, the above recommendations will help.</DIV> =
<DIV> </DIV> <DIV>Rand</DIV> <DIV> </DIV> <BLOCKQUOTE style=3D"=
PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #00=
0000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt Arial">-----=
Original Message -----</DIV> <DIV style=3D"BACKGROUND: #e4e4e4; FONT: 10=
pt Arial; COLOR: black"><B>From:</B> SquishyGecko</DIV> <DIV style=3D"FON=
T: 10pt Arial"><B>Sent:</B> Tuesday, May 11, 2004 4:03 PM</DIV> <DIV styl=
e=3D"FONT: 10pt Arial"><B>To:</B> listserv@azgeocaching.com</DIV> <DIV st=
yle=3D"FONT: 10pt Arial"><B>Subject:</B> [Az-Geocaching] Help with a TB l=
og</DIV> <DIV> </DIV>Okay, so yesterday AZcachemeister archived his =
"Mine's Bigger" cache and<BR>delivered the TBs to GCJCQ0. This morn=
ing I went created a log on one of my<BR>TBs as "Grabbed it from somewher=
e else" and just before I wrote a note on<BR>GCJCQ0 to log it as being th=
ere, Team Red Dog posted a log that they'd<BR>retrieved it. So I de=
leted my log entry on the TB, however it still shows<BR>as being in my in=
ventory. How on earth do I fix this? My immediate thought<BR>=
is to log a note on GCJCQ0 dropping it off, and have Team Red Dog log it =
as<BR>retrieved again. Any thoughts?<BR><BR><BR>---<BR>Outgoing mai=
l is certified Virus Free.<BR>Checked by AVG anti-virus system (http://ww=
w.grisoft.com).<BR>Version: 6.0.679 / Virus Database: 441 - Release Date:=
5/9/2004<BR><BR>________________________________________________________=
____<BR>Az-Geocaching mailing list listserv@azgeocaching.com<BR>To edit y=
our setting, subscribe or unsubscribe visit:<BR>http://listserv.azgeocach=
ing.com/mailman/listinfo/az-geocaching<BR><BR>Arizona's Geocaching Resour=
ce<BR>http://www.azgeocaching.com<BR></BLOCKQUOTE></BODY></HTML>
------=_NextPart_001_0000_01C43777.CA46F3E0--