Re: Database Anomaly


Hi Rich,

You made my point for me. It is the YaDDNet database with the anomaly!

And that matters less to me than finding out what the 'LJ2B' is for, in two notionally separate locations.

BR, David

-----Original Message-----

If I could shove in my two-penny-worth

As a station's name doesn't form part of the DSC message, in theory
there's nothing to stop you calling it anything you want (within
reason, I suppose!) if you keep the info to yourself.
Once you start sharing, that's when problems could occur Whose
database do we use as 'the one we must all adhere to' and why? One
man's 'Sailor Examiner' could well be another man's 'Pandrup Test',
for example.Same MMSI number, different name. My own coast station
database for DSC Decoder shows the UK coastguard stations with their
names plus a simple "CG" suffix, and shore stations using ships' MMSI
numbers have an asterisk at the beginning and end of their names so I
can spot them easily when I'm looking at the DSC decoder screen. A
problem would occur if that was how YADDNet read it as someone else
might well have the same station with a different name, e.g 002320011
is Solent CG to me but it could well Solent COASTGUARD to someone else
and could result in duplicate entries which would take up oodles of
unnecessary space on the server. This duplication doesn't happen as
John has got some trickery installed in the heart of YADDNet to ensure
that irrespective of what your database may say and what gets uploaded
to YADDNet, it will be crunched saved and output to your own RWW
report using the station name from the YADD database, not yours. The
databases my well be the same but this is done just in case they're
not. Clever dot com

I've no idea what happens when my weekly log gets uploaded to REU. I
just 'send and forget' !

As for the LJ2B callsign....PASS !


Join to automatically receive all group messages.