wondering if
you can make the database time dependent for contests.
Ie having a "since" button or something similiar in order to only
look at qsos since a certain date /time .
right now i have to create a new database in my log and then have
jtalert scan it for every contest,
the worst part is i have to import the contest log into my main
log afterward and then rescan it.
maybe you have something already set up? as i really only want one
log
OM,
What Log type are you using with JTAlert?
You have a three options depending on how you want to approach the
contest.
If your contest participation is to work
as many stations and multipliers as possible without any
regard to you're current JTAlert needs. Start the contest with
a new empty log then do a one-off Alert database rebuild which
will take a second or two since the log is empty. At the end
of the contest if you want to put the contest QSOs in your
normal JTAlert log do an import of the contest QSOs. How you
do that depends on the log type you're using, followed by an
Alert database rebuild operation after switching back to your
normal JTAlert log.
If you're in the contest to pick up new
ones as well as hand out numbers, set the JTAlert Worked B4
date to the date of the start of the contest. This will
ensure that past QSOs before the contest will not be flagged
as B4s and you will still be alerted to new ones you need.
QSOs logged during the contest will be flagged as B4s. After
the contest turn off the Worked B4 date. There is no
need for an Alert database rebuild.
If you're in the
contest only to pickup new ones without any desire to work as many stations and multipliers as
possible, you don't need to make any changes in JTAlert
and treat the contest as just another day working the
bands.
1. & 2. are essentially the same, except
1. leaves you with a dedicated contest log that you can use for
submission and saving.
