Hi Guys, I have read all the posts on this topic and everyone's suggestions are all valid for why you might have experienced this. Those ideas involving user input errors of course the user can be careful about, those suggesting MS Access Jet engine are valid too but unfortunately I don't know what we could do about that. I'll keep an eye on it from this end too in the hope of catching something repeatedable... But, unlike all you power ops, I don't get that many cards... hihi....
Cheers, Jack ----- Original Message ----- From: "Clark L. Stewart" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, January 22, 2007 4:52 PM Subject: Re: [Dxbase] Previous QSOs Guys, Here is "one" possible explanation. If you should accidently hit the space bar and enter a blank space character before you type the callsign in the "Value to Find" box, DXbase will NOT find the callsign. It will LOOK absolutely perfect to your eye but the program is trying to find a value that starts with a blank space character and therefore it will not find the call sign you are want. Try this, if you search for a call and it is not found, just RE-ENTER the call, making certain there is not a leading space and search for it again. Another possible explanation for this problem is if you type the letter "O" instead of the number "?" then DXbase will not find that callsign either. Clark, W8TN At 01:14 PM 1/22/2007 -0500, GRW wrote: >Bill, same problem here as well. I also went looking by date, and sure >enough, it was in the log! Not sure why this happnes only sometimes????? > >Gary/N8AYY > >----- Original Message ----- >From: "Bill Parry" <[EMAIL PROTECTED]> >To: <[email protected]> >Sent: Monday, January 22, 2007 10:55 AM >Subject: [Dxbase] Previous QSOs > > >I was doing my monthly QSLing chores and had a funny thing happen. I was in >the Previous QSOs window, calling up contacts one at a time to match the >cards from the bureau. I always have a small number that think they worked >me but are not in the log. I lay them aside and look back thru my log at >the >time they say I worked them. > >This morning, and I believe that this may have happened before, I typed >VE6SH into the window and no QSOs came back. This was the last QSL so I >left >the Previous QSOs screen up and then looked at the date and time noted on >the log window. The QSO was there in the log! I thought maybe I mis-typed >either in the Previous QSO Window or in the log... Nope, all OK. I >minimumized the log window and now the Previous QSO window has this QSO >plus >6 others that were also in the log. > >Is this something that has already been discussed, am I doing something >dumb, ...? > >Bill, W5VX ______________________________________________________________ Dxbase mailing list Home: http://mailman.qth.net/mailman/listinfo/dxbase Help: http://mailman.qth.net/mmfaq.htm Post: mailto:[email protected]
