Page 1 of 1

Fields QSL sent/rcvd via

Posted: 28 Feb 2014, 06:54
by PB4FUN
If you edit a QSO and set either the field QSL sent via or QSL received via to e.g. Via Bureau and store it, you cannot undo it to null.

Re: Fields QSL sent/rcvd via

Posted: 28 Feb 2014, 07:09
by G4POP
I have just tried this and it worked without issue!

Please detail where and how you are setting and un-setting the QSL status

Re: Fields QSL sent/rcvd via

Posted: 28 Feb 2014, 15:09
by IW3HMH
Using drop down lists it's correct: you cannot "undo" to null.
This is because those fields are mandatory, and because they cover all possible situations. The field "received via" doesn't make sense if the QSL has not been received yet, and should be ignored.

Re: Fields QSL sent/rcvd via

Posted: 01 Mar 2014, 07:59
by PB4FUN
[QslSentVia] nvarchar(50) NULL,

What is mandatory about that ?
And ofcourse it is possible to set a db field to null again when you have a cbo textvalue of ""

Re: Fields QSL sent/rcvd via

Posted: 02 Mar 2014, 22:44
by IW3HMH
One thing is how the field is made, one is how the field is used by the software. When I set blank I will not set field as null.
Anyway I will check if allowing blank in this field is ok. Theoretically if the field is an enumeration it must (or, maybe, it's better) if it has a value on it... but we know ADIF has some design flaws :-)

Re: Fields QSL sent/rcvd via

Posted: 04 Mar 2014, 22:29
by PB4FUN
TQSent = enum (qslNothing = 0, qslViaBurea = 2, qslViaLotW = 4, qslViaEQSl = 8, qslDirect = 16)

Using this structure you can even mark sending/receiving QSL by multiple ways.
In that case you can mark the QSL sent by 14 and received by 18

Or you can set it back to 0 :-)

If you do so you might have some issues with the date sent/received that will be dates and need more fields or a seperate table with those multiple dates.

Re: Fields QSL sent/rcvd via

Posted: 04 Mar 2014, 23:08
by IW3HMH
Yes, i know the use of flags :D
The "main" limit is due to our base choice, that was (initially) to make a database based on ADIF format, and strictly related to this.

This approach was good enough for some years, but now it's a little bit too strict for our needs, and we're about to leave this strong relation.
One of our "limits" is we must keep compatibility and be able to reconstruct the whole database from an adif import. We can use "application fields" in adif export, but those fields are of limited use. Also changing the database structure it's not so easy, if you want to keep a flawless migration between different user versions :)

Re: Fields QSL sent/rcvd via

Posted: 05 Mar 2014, 18:19
by PB4FUN
Sure,but with an import you have only one, and with an export you can let the user decide in the settings with a preferred sent/received by.
In that case if you have 18 as flag check in the settings what of those is most preferred, and if direct > Bureau export the Direct value to adif.

Re: Fields QSL sent/rcvd via

Posted: 06 Mar 2014, 13:52
by IW3HMH
what about exporting this field only when received is YES or VERIFIED? :)

73
Daniele