Topics

DXKeeper 1.1.6 is available

Dave Bernstein <dhb@...>
 

DXKeeper 1.1.6 corrects a defect that prevents addition of the first
QSO to a log via the Capture Window. This release also includes
further improvements to the online help.

If you've already installed DXKeeper 1.1.1 or later, you can upgrade
to version 1.1.6 by downloading and then running
www.qsl.net/dxkeeper/DXKeeper116Update.exe -- your online help will
automatically be update by this process.

If a previous version of DXKeeper is not already installed on your
PC, you can obtain this release via
http://www.qsl.net/dxkeeper/download.htm .

73,

Dave, AA6YQ

Richard B Drake
 

Dave,

I am still having a problem with the Progress Table not showing
correct results for imported log entries. I did a little more
research and found that the only entries that were appearing in
the table were QSO's marked confirmed. The table contains all
"F's" and no "W's". All the DXCC prefixes for worked but not
confirmed countries look correct. As a test, I entered a new
country in the capture window and logged it. Indeed, that contact
now shows up as the only "W" in the progress table. Doing a
recompute doesn't change things. I have no idea what's going on
but maybe that's clue for you. If you like I can zip up a copy of
my mdb file and mail it to you.

----
73, Rich - W3ZJ

Dave, AA6YQ <dhb@...>
 

That's a pretty good clue, Rich -- it implies that the import operation is
not properly handling worked-but-not-confirmed QSOs. I've imported my 13K
QSOs (from the first-generation DXLab, which began life as an alternative
user interface for log files created by LOGic) and the
worked/confirmed/verified numbers match exactly, but perhaps your logging
program does things a bit differently, ADIF not withstanding.

Could you send me the ADIF file you're importing, or at least a fragment
containing several worked-but-not-confirmed QSOs?

Was the import operation reliable? How was import performance?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 12:17 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

I am still having a problem with the Progress Table not showing
correct results for imported log entries. I did a little more
research and found that the only entries that were appearing in
the table were QSO's marked confirmed. The table contains all
"F's" and no "W's". All the DXCC prefixes for worked but not
confirmed countries look correct. As a test, I entered a new
country in the capture window and logged it. Indeed, that contact
now shows up as the only "W" in the progress table. Doing a
recompute doesn't change things. I have no idea what's going on
but maybe that's clue for you. If you like I can zip up a copy of
my mdb file and mail it to you.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Richard B Drake
 

Dave,

The import went fine, except for the program error that occurs at
QSO #3757. I found that all I have to do to recover from that is
to close and reopen DXKeeper, then start the import again. The
first 3757 are then duplicates and after passing those it
completes normally. Performance is much improved. I'll send you
the entire ADIF file (privately) so you can see that too.

---
73, Rich - W3ZJ

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, March 24, 2001 12:33 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


That's a pretty good clue, Rich -- it implies that the
import operation is
not properly handling worked-but-not-confirmed QSOs.
I've imported my 13K
QSOs (from the first-generation DXLab, which began life
as an alternative
user interface for log files created by LOGic) and the
worked/confirmed/verified numbers match exactly, but
perhaps your logging
program does things a bit differently, ADIF not withstanding.

Could you send me the ADIF file you're importing, or at
least a fragment
containing several worked-but-not-confirmed QSOs?

Was the import operation reliable? How was import performance?

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 12:17 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

I am still having a problem with the Progress Table
not showing
correct results for imported log entries. I did a little more
research and found that the only entries that were
appearing in
the table were QSO's marked confirmed. The table contains all
"F's" and no "W's". All the DXCC prefixes for worked but not
confirmed countries look correct. As a test, I entered a new
country in the capture window and logged it. Indeed,
that contact
now shows up as the only "W" in the progress table. Doing a
recompute doesn't change things. I have no idea
what's going on
but maybe that's clue for you. If you like I can zip
up a copy of
my mdb file and mail it to you.

----
73, Rich - W3ZJ


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/


Dave, AA6YQ <dhb@...>
 

The progress problem is a defect that was easily fixed; I'll send you a
progress report file so youc an verify that this was the only problem.

I noticed a lot of "truncated name" messages. With the "Import from Logger"
box checked, I look for names and qths being concatenated in the name field,
separated by a colon; its easy to split these and place the name and QTH in
their proper fields. But there are lots of situations where the name field
contains contest info, or names and QTHs without a separating colon. In
DXView117, I added code to detect this condition and put the contents of the
name field into the comment field (where there is plenty of room); let me
know if you think this is a bad idea, or have a better suggestion.

I've imported your .ADI files several times without a crash, but clearly
there's a latent defect. I'll take a look at QSO# 3757 to see if it contains
anything unusual, and will add instrumentation to 117 so that we can track
it down.

Has CI-V Commander created any error log files for you when you rapidly QSY
your TenTec?

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 13:32 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

The import went fine, except for the program error that occurs at
QSO #3757. I found that all I have to do to recover from that is
to close and reopen DXKeeper, then start the import again. The
first 3757 are then duplicates and after passing those it
completes normally. Performance is much improved. I'll send you
the entire ADIF file (privately) so you can see that too.

---
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave, AA6YQ [mailto:dhb@...]
> Sent: Saturday, March 24, 2001 12:33 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> That's a pretty good clue, Rich -- it implies that the
> import operation is
> not properly handling worked-but-not-confirmed QSOs.
> I've imported my 13K
> QSOs (from the first-generation DXLab, which began life
> as an alternative
> user interface for log files created by LOGic) and the
> worked/confirmed/verified numbers match exactly, but
> perhaps your logging
> program does things a bit differently, ADIF not withstanding.
>
> Could you send me the ADIF file you're importing, or at
> least a fragment
> containing several worked-but-not-confirmed QSOs?
>
> Was the import operation reliable? How was import performance?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 12:17 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> I am still having a problem with the Progress Table
> not showing
> correct results for imported log entries. I did a little more
> research and found that the only entries that were
> appearing in
> the table were QSO's marked confirmed. The table contains all
> "F's" and no "W's". All the DXCC prefixes for worked but not
> confirmed countries look correct. As a test, I entered a new
> country in the capture window and logged it. Indeed,
> that contact
> now shows up as the only "W" in the progress table. Doing a
> recompute doesn't change things. I have no idea
> what's going on
> but maybe that's clue for you. If you like I can zip
> up a copy of
> my mdb file and mail it to you.
>
> ----
> 73, Rich - W3ZJ
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Richard B Drake
 

Yes, of course I saw that too and Logger is a bit flaky on that
score because it doesn't have separate fields for name and QTH and
the exports the comment field with the <NAME> tag. I could see
what your difficulty was there and actually I thought you did a
pretty good job of unscrambling the mess. Keep in mind that Logger
does not require a colon between the name and the rest of the
comment field, the only real separator is white space. Some of my
entries have a colon because they were imported from yet another
logging program that I used early on. More recent entries that
were made directly into Logger do not have a colon. That may help
you as you attempt to refine the parsing process but you'll never
get it perfect. That comment field is totally free form and can
contain almost anything. Most of my entries do have "name" as the
first word but what comes after that is anybody's guess, it's not
necessarily QTH, in fact I only rarely log QTH.

----
73, Rich - W3ZJ

I noticed a lot of "truncated name" messages. With the
"Import from Logger"
box checked, I look for names and qths being
concatenated in the name field,
separated by a colon; its easy to split these and place
the name and QTH in
their proper fields. But there are lots of situations
where the name field
contains contest info, or names and QTHs without a
separating colon. In
DXView117, I added code to detect this condition and
put the contents of the
name field into the comment field (where there is
plenty of room); let me
know if you think this is a bad idea, or have a better
suggestion.

I've imported your .ADI files several times without a
crash, but clearly
there's a latent defect. I'll take a look at QSO# 3757
to see if it contains
anything unusual, and will add instrumentation to 117
so that we can track
it down.

Has CI-V Commander created any error log files for you
when you rapidly QSY
your TenTec?

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 13:32 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Dave,

The import went fine, except for the program error
that occurs at
QSO #3757. I found that all I have to do to recover
from that is
to close and reopen DXKeeper, then start the import again. The
first 3757 are then duplicates and after passing those it
completes normally. Performance is much improved.
I'll send you
the entire ADIF file (privately) so you can see that too.

---
73, Rich - W3ZJ

> -----Original Message-----
> From: Dave, AA6YQ [mailto:dhb@...]
> Sent: Saturday, March 24, 2001 12:33 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> That's a pretty good clue, Rich -- it implies that the
> import operation is
> not properly handling worked-but-not-confirmed QSOs.
> I've imported my 13K
> QSOs (from the first-generation DXLab, which began life
> as an alternative
> user interface for log files created by LOGic) and the
> worked/confirmed/verified numbers match exactly, but
> perhaps your logging
> program does things a bit differently, ADIF not
withstanding.
>
> Could you send me the ADIF file you're importing, or at
> least a fragment
> containing several worked-but-not-confirmed QSOs?
>
> Was the import operation reliable? How was import
performance?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 12:17 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> I am still having a problem with the Progress Table
> not showing
> correct results for imported log entries. I did a
little more
> research and found that the only entries that were
> appearing in
> the table were QSO's marked confirmed. The table
contains all
> "F's" and no "W's". All the DXCC prefixes for
worked but not
> confirmed countries look correct. As a test, I
entered a new
> country in the capture window and logged it. Indeed,
> that contact
> now shows up as the only "W" in the progress
table. Doing a
> recompute doesn't change things. I have no idea
> what's going on
> but maybe that's clue for you. If you like I can zip
> up a copy of
> my mdb file and mail it to you.
>
> ----
> 73, Rich - W3ZJ
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>


Yahoo! Groups Sponsor



To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/


Dave, AA6YQ <dhb@...>
 

If there's no standard for how the information is jammed together, then it
will be difficult to satisfy everyone. Sounds like "Import from Logger"
should mean "place the contents of the name field into the comments field",
or maybe "place everything after the first word of the name field into the
comments field".

I'll leave it as it is for now, but suggests would be greatly appreciated...

73,

Dave, AA6YQ

-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 15:58 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Yes, of course I saw that too and Logger is a bit flaky on that
score because it doesn't have separate fields for name and QTH and
the exports the comment field with the <NAME> tag. I could see
what your difficulty was there and actually I thought you did a
pretty good job of unscrambling the mess. Keep in mind that Logger
does not require a colon between the name and the rest of the
comment field, the only real separator is white space. Some of my
entries have a colon because they were imported from yet another
logging program that I used early on. More recent entries that
were made directly into Logger do not have a colon. That may help
you as you attempt to refine the parsing process but you'll never
get it perfect. That comment field is totally free form and can
contain almost anything. Most of my entries do have "name" as the
first word but what comes after that is anybody's guess, it's not
necessarily QTH, in fact I only rarely log QTH.

----
73, Rich - W3ZJ

> I noticed a lot of "truncated name" messages. With the
> "Import from Logger"
> box checked, I look for names and qths being
> concatenated in the name field,
> separated by a colon; its easy to split these and place
> the name and QTH in
> their proper fields. But there are lots of situations
> where the name field
> contains contest info, or names and QTHs without a
> separating colon. In
> DXView117, I added code to detect this condition and
> put the contents of the
> name field into the comment field (where there is
> plenty of room); let me
> know if you think this is a bad idea, or have a better
> suggestion.
>
> I've imported your .ADI files several times without a
> crash, but clearly
> there's a latent defect. I'll take a look at QSO# 3757
> to see if it contains
> anything unusual, and will add instrumentation to 117
> so that we can track
> it down.
>
> Has CI-V Commander created any error log files for you
> when you rapidly QSY
> your TenTec?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 13:32 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> The import went fine, except for the program error
> that occurs at
> QSO #3757. I found that all I have to do to recover
> from that is
> to close and reopen DXKeeper, then start the import again. The
> first 3757 are then duplicates and after passing those it
> completes normally. Performance is much improved.
> I'll send you
> the entire ADIF file (privately) so you can see that too.
>
> ---
> 73, Rich - W3ZJ
>
> > -----Original Message-----
> > From: Dave, AA6YQ [mailto:dhb@...]
> > Sent: Saturday, March 24, 2001 12:33 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > That's a pretty good clue, Rich -- it implies that the
> > import operation is
> > not properly handling worked-but-not-confirmed QSOs.
> > I've imported my 13K
> > QSOs (from the first-generation DXLab, which began life
> > as an alternative
> > user interface for log files created by LOGic) and the
> > worked/confirmed/verified numbers match exactly, but
> > perhaps your logging
> > program does things a bit differently, ADIF not
> withstanding.
> >
> > Could you send me the ADIF file you're importing, or at
> > least a fragment
> > containing several worked-but-not-confirmed QSOs?
> >
> > Was the import operation reliable? How was import
> performance?
> >
> > 73,
> >
> > Dave, AA6YQ
> > -----Original Message-----
> > From: Richard B Drake [mailto:rich@...]
> > Sent: Saturday, March 24, 2001 12:17 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > Dave,
> >
> > I am still having a problem with the Progress Table
> > not showing
> > correct results for imported log entries. I did a
> little more
> > research and found that the only entries that were
> > appearing in
> > the table were QSO's marked confirmed. The table
> contains all
> > "F's" and no "W's". All the DXCC prefixes for
> worked but not
> > confirmed countries look correct. As a test, I
> entered a new
> > country in the capture window and logged it. Indeed,
> > that contact
> > now shows up as the only "W" in the progress
> table. Doing a
> > recompute doesn't change things. I have no idea
> > what's going on
> > but maybe that's clue for you. If you like I can zip
> > up a copy of
> > my mdb file and mail it to you.
> >
> > ----
> > 73, Rich - W3ZJ
> >
> >
> > Yahoo! Groups Sponsor
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to the Yahoo!
> > Terms of Service.
> >
> >
> >
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Richard B Drake
 

I think the answer that would best satisfy the most people (and
certainly me), is place the first word in the name field and every
thing else in the comment field. It won't be 100% but it will be
right more often than wrong.

----
73, Rich

-----Original Message-----
From: Dave, AA6YQ [mailto:dhb@...]
Sent: Saturday, March 24, 2001 17:28 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


If there's no standard for how the information is
jammed together, then it
will be difficult to satisfy everyone. Sounds like
"Import from Logger"
should mean "place the contents of the name field into
the comments field",
or maybe "place everything after the first word of the
name field into the
comments field".

I'll leave it as it is for now, but suggests would be
greatly appreciated...

73,

Dave, AA6YQ
-----Original Message-----
From: Richard B Drake [mailto:rich@...]
Sent: Saturday, March 24, 2001 15:58 PM
To: dxlab@...
Subject: RE: [dxlab] DXKeeper 1.1.6 is available


Yes, of course I saw that too and Logger is a bit
flaky on that
score because it doesn't have separate fields for
name and QTH and
the exports the comment field with the <NAME> tag. I could see
what your difficulty was there and actually I thought
you did a
pretty good job of unscrambling the mess. Keep in
mind that Logger
does not require a colon between the name and the rest of the
comment field, the only real separator is white
space. Some of my
entries have a colon because they were imported from
yet another
logging program that I used early on. More recent entries that
were made directly into Logger do not have a colon.
That may help
you as you attempt to refine the parsing process but
you'll never
get it perfect. That comment field is totally free
form and can
contain almost anything. Most of my entries do have
"name" as the
first word but what comes after that is anybody's
guess, it's not
necessarily QTH, in fact I only rarely log QTH.

----
73, Rich - W3ZJ

> I noticed a lot of "truncated name" messages. With the
> "Import from Logger"
> box checked, I look for names and qths being
> concatenated in the name field,
> separated by a colon; its easy to split these and place
> the name and QTH in
> their proper fields. But there are lots of situations
> where the name field
> contains contest info, or names and QTHs without a
> separating colon. In
> DXView117, I added code to detect this condition and
> put the contents of the
> name field into the comment field (where there is
> plenty of room); let me
> know if you think this is a bad idea, or have a better
> suggestion.
>
> I've imported your .ADI files several times without a
> crash, but clearly
> there's a latent defect. I'll take a look at QSO# 3757
> to see if it contains
> anything unusual, and will add instrumentation to 117
> so that we can track
> it down.
>
> Has CI-V Commander created any error log files for you
> when you rapidly QSY
> your TenTec?
>
> 73,
>
> Dave, AA6YQ
> -----Original Message-----
> From: Richard B Drake [mailto:rich@...]
> Sent: Saturday, March 24, 2001 13:32 PM
> To: dxlab@...
> Subject: RE: [dxlab] DXKeeper 1.1.6 is available
>
>
> Dave,
>
> The import went fine, except for the program error
> that occurs at
> QSO #3757. I found that all I have to do to recover
> from that is
> to close and reopen DXKeeper, then start the
import again. The
> first 3757 are then duplicates and after passing those it
> completes normally. Performance is much improved.
> I'll send you
> the entire ADIF file (privately) so you can see that too.
>
> ---
> 73, Rich - W3ZJ
>
> > -----Original Message-----
> > From: Dave, AA6YQ [mailto:dhb@...]
> > Sent: Saturday, March 24, 2001 12:33 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > That's a pretty good clue, Rich -- it implies that the
> > import operation is
> > not properly handling worked-but-not-confirmed QSOs.
> > I've imported my 13K
> > QSOs (from the first-generation DXLab, which began life
> > as an alternative
> > user interface for log files created by LOGic) and the
> > worked/confirmed/verified numbers match exactly, but
> > perhaps your logging
> > program does things a bit differently, ADIF not
> withstanding.
> >
> > Could you send me the ADIF file you're importing, or at
> > least a fragment
> > containing several worked-but-not-confirmed QSOs?
> >
> > Was the import operation reliable? How was import
> performance?
> >
> > 73,
> >
> > Dave, AA6YQ
> > -----Original Message-----
> > From: Richard B Drake [mailto:rich@...]
> > Sent: Saturday, March 24, 2001 12:17 PM
> > To: dxlab@...
> > Subject: RE: [dxlab] DXKeeper 1.1.6 is available
> >
> >
> > Dave,
> >
> > I am still having a problem with the Progress Table
> > not showing
> > correct results for imported log entries. I did a
> little more
> > research and found that the only entries that were
> > appearing in
> > the table were QSO's marked confirmed. The table
> contains all
> > "F's" and no "W's". All the DXCC prefixes for
> worked but not
> > confirmed countries look correct. As a test, I
> entered a new
> > country in the capture window and logged it. Indeed,
> > that contact
> > now shows up as the only "W" in the progress
> table. Doing a
> > recompute doesn't change things. I have no idea
> > what's going on
> > but maybe that's clue for you. If you like I can zip
> > up a copy of
> > my mdb file and mail it to you.
> >
> > ----
> > 73, Rich - W3ZJ
> >
> >
> > Yahoo! Groups Sponsor
> >
> >
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to the Yahoo!
> > Terms of Service.
> >
> >
> >
> >
> >
> >
> > ------------------------ Yahoo! Groups Sponsor
> >
> > To unsubscribe from this group, send an email to:
> > dxlab-unsubscribe@...
> >
> >
> >
> > Your use of Yahoo! Groups is subject to
> > http://docs.yahoo.com/info/terms/
> >
> >
> >
>
>
> Yahoo! Groups Sponsor
>
>
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo!
> Terms of Service.
>
>
>
>
>
>
> ------------------------ Yahoo! Groups Sponsor
>
> To unsubscribe from this group, send an email to:
> dxlab-unsubscribe@...
>
>
>
> Your use of Yahoo! Groups is subject to
> http://docs.yahoo.com/info/terms/
>
>
>


Yahoo! Groups Sponsor

iWin.com - The Place to Win Stuff!


To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to the Yahoo!
Terms of Service.






------------------------ Yahoo! Groups Sponsor

To unsubscribe from this group, send an email to:
dxlab-unsubscribe@...



Your use of Yahoo! Groups is subject to
http://docs.yahoo.com/info/terms/