On Thu, 27 Apr 2000, Hamish Moffatt wrote:
> Well, the list of fields I want is quite big. None of the Windows
> programs has all of them, which is part of the reason I'm considering
> home brew.
>
> Things commonly lacking in existing log programs
> * no separate name and QTH fields (some programs expect you to put these
> in the comments; I prefer separate fields)
> * mode field of 3 or 4 characters with a fixed list (I mostly operate
> Hellschreiber which has a lot of sub-modes like "PSKHELL245" and
> "FELDHELL", just as SSTV has "Martin M1", "Robot 36" etc,
> and I would like to log the exact mode used).
>
> I also like to log the transmit power used both by my station and
> the remote station. (This is getting into the very picky category.)
> One program I do like for Windows has a field for my transmit power,
> but not the other op's.
Those all sound to me like ones I would want as well.
> Contesting? Difficult to build a program that does both contesting
> and casual logging well I think.
One frontend yes, one database no.
I can see a front end optimised for casual loggins, one for contesting, one
for detailed logging, one for Net operations, etc. All from the same database
so I can be a casual logger with one interface, and still have a seperate
interface to handle Net operations or the occasional contest.
I have a friend who is seriously into traffic nets, he acts as net control for
several each week. He needs to log things like , what net(s) does an individual
belong to, did they log in today (yesterday, last week, etc.), how much
traffic they had, etc., and generate monthly reports.
Shawn (kb7pwd) has mentioned his nettebook program. While I've not had
a chance to actually run it yet, it looks like maybe a good starting point.
Besides. he obviously understands this database stuff better than I do. :-)
I'm an embedded systems guy, it's not often I need a fancy DB.
Ken, N7IPB
