Once again Jack-to-the-rescue. When I turn off Auto Screen Look Up in the User Options the problem goes away. Turn it back on, it comes back.
I am using the QRZ CD program copied on to the hard drive. It is the QRZ32 ver2.0 with the Version 30 database Winter 2007/8. When I run the QRZ look up to search for OH4A it hangs. Uninstalling and re-installing the QRZ program from the original CD does not correct the problem. Does anyone out there have the same version of QRZ that can run a look up of OH4A? Time to send a email to the QZR folks I guess. Thanks to all who offered help and thanks to Jack for the fix. 73, Dale, AA1QD ----- Original Message ----- From: "Jack" <[EMAIL PROTECTED]> To: "D. Drake" <[EMAIL PROTECTED]>; "DxBase Refector" <[email protected]> Sent: Monday, February 18, 2008 10:00 AM Subject: Re: [Dxbase] Help with Corrupt Database > Dale, > > Based on what you say you have already done, it doesn't sound like you > have any DXbase database corruption. A final test would be to initialize > tables and if you don't get any errors, and nothing else in the software > seems out of place, I would say the database is fine. I would then > suspect that it may have something to do with the address lookups that > also take place when you enter a callsign. Perhaps there is a bad record > stored on whatever CDROM address database you are using. Such a thing has > been found in the past as I recall but don't remember what callsign was > involved. You could try turning off address lookups temporarily and see > if the problem goes away. Even if you prove this to be the case, there > isn't much we can do about it, but at least you'll know. > > Cheers, > Jack > > ----- Original Message ----- > From: "D. Drake" <[EMAIL PROTECTED]> > To: "DxBase Refector" <[email protected]> > Sent: Monday, February 18, 2008 8:52 AM > Subject: [Dxbase] Help with Corrupt Database > > >>I have run into an apparent corruption problem with my DxBase 2007 >>database that I am unable to solve. Symptoms follow- >> >> When I enter the callsign OH4A in the log table and hit the tab key the >> program locks up. The cursor freezes in the call sign block. The rest of >> the data that normally fills in for the log entry line when hitting tab >> fills in OK and the previous QSO window populates with the previous OH4A >> qso's OK. >> >> It is repeatable 100% of the time. >> >> It only happens with that specific call sign, i.e. entering OH2A or OH4AA >> etc has no similar effect. >> >> There are 4 previous log entries with OH4A. When I use the Edit Find >> function to locate those entries the program locks up once the focus in >> the logging window shifts to that callsign block. >> >> >> >> >> I have used the repair corrupted database procedure from the help file 3 >> times with no success. I even deleted all of the log entries for OH4A, >> re-performed the corrupted database procedure and the problem persists. >> There are no errors shown when I run the dxbase import utility. >> >> I have examined the log database mdb file and the refdata.mdb file in >> Microsoft Access and can find no apparent problems in any of the tables. >> >> >> I would very much appreciate any thoughts on how to further troubleshoot >> the problem. >> >> Thanks, >> >> Dale, AA1QD >> >> >> >> ______________________________________________________________ >> Dxbase mailing list >> Home: http://mailman.qth.net/mailman/listinfo/dxbase >> Help: http://mailman.qth.net/mmfaq.htm >> Post: mailto:[email protected] >> > > >
