Worked E7/DK6XZ in the ARRL CW test over the week end using N1MM Logger. Exported log to an ADIF file. Imported the log to DXBase 2005. Received an error message that the call is invalid. I found out that T9 is now E7. I apparently missed the upgrade. What is the data for putting the information into the Database Access / Country Prefixes? TKS JV From [EMAIL PROTECTED] Mon Feb 18 10:00:38 2008 From: [EMAIL PROTECTED] (Jack) Date: Mon Feb 18 10:05:55 2008 Subject: [Dxbase] Help with Corrupt Database References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]>
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] >
