[LOGic] Data type mismatch

[Sante - IK0HBN]

Thanks Mel.
Below there are both the report files done by four hands, NN8L Hal 
and IK0CHU Mauro. Sure we will find a lot of pairs of eyes to look at 
them.. .-)
I remenber that the problem was only when the FREQ was missing and 
only Band was available. The first Band instance was repeated also 
for the following qso's inside the same card.
TIA to all
Sante




At 23.48 11/01/2009, you wrote:
>While I am a programmer, I am not a Foxpro programmer, but I could take
>a look. Sometimes a second pair of eyes might spot something...
>
>Sante - IK0HBN wrote:
> > Thank you Mel,
> > can you give a look at my card report and understand why Logic
> > repeated the same band for all the qso within the same card, if Freq
> > was not specified?
> > If you agree I could send my file.
> > TIA
> > Sante
> >
> >
> > At 21.23 11/01/2009, you wrote:
> >> No quotes around frequency... it is numeric, not a string.
> >>
> >>
> >> ----- Original Message -----
> >> From: "Sante - IK0HBN" <ik0hbn at libero.it>
> >> To: <logic at mailman.qth.net>
> >> Sent: Saturday, January 10, 2009 7:07 PM
> >> Subject: [LOGic] Data type mismatch
> >>
> >>
> >>> Hi guys,
> >>> may you help me in troubleshooting this error?
> >>> One step back....
> >>>
> >>> Mauro, IK0CHU helped me at putting at work a report done by Hal, NN8L
> >>> some years ago that I should use to print qso's direct on qsl card.
> >>> My card accepts till 4 qso's for card, so we were able to print them
> >>> without problem, putting the FREQ read on the log directly on the card.
> >>>
> >>> As I began with radio more than 20 years ago, old logging program did
> >>> not save the frequency in the log itself, so Mauro put an expression
> >>> that filled the missing frequency with the band, eg 20M, 15M and so on.
> >>>
> >>> If I had only a qso with BAND printed on the card, everthing runs
> >>> fine here, but if I have more than a qso to have printed on the card,
> >>> if this /these qos's had the band to be printed too,
> >>> the result was having the first qso with the correct band on the
> >>> card, and from the second to the fourth, if exist, having the same
> >>> band of the first qso.
> >>> EG.
> >>> 1 qso: 20M (OK)
> >>> 2 qso: 15M (got printed 15M)
> >>> 3 qso: 40M  got printed 15M).
> >>> As unable to fix the report, we thought to put a "static frequency"
> >>> in all the FREQ field having care to respect bandplan, so:
> >>> 1 qso on 14 CW, should write 14.000
> >>> 1 qso on 14 RTTY , 14090
> >>> 1 qso on ssb 14250,
> >>> so to force the report to print the frequency on the card. We use
> >>> MASS CHANGE in ADVANCED
> >>> We did the following expression:
> >>> replace freq with "14.243" for BAND='20M' AND EMPTY(FREQ) AND MODE='SSTV'
> >>>
> >>> but we got Data type Mismatch.
> >>> Any idea for both the problem or even the last one?
> >>> Thank you
> >>> Sante
> >>>
> >>>
> >>> _______________________________________________
> >>> LOGic mailing list
> >>> LOGic at mailman.qth.net
> >>> http://mailman.qth.net/mailman/listinfo/logic
> >> _______________________________________________
> >> LOGic mailing list
> >> LOGic at mailman.qth.net
> >> http://mailman.qth.net/mailman/listinfo/logic
> >
> > _______________________________________________
> > LOGic mailing list
> > LOGic at mailman.qth.net
> > http://mailman.qth.net/mailman/listinfo/logic
> >
>
>--
>Mel, VE2DC
>_______________________________________________
>LOGic mailing list
>LOGic at mailman.qth.net
>http://mailman.qth.net/mailman/listinfo/logic
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IK0CHU.rep
Type: application/octet-stream
Size: 1986 bytes
Desc: not available
Url : http://mailman.qth.net/pipermail/logic/attachments/20090112/1701f66b/attachment-0002.obj 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: IK0CHU.FPT
Type: application/octet-stream
Size: 22104 bytes
Desc: not available
Url : http://mailman.qth.net/pipermail/logic/attachments/20090112/1701f66b/attachment-0003.obj