[Dxbase] Help with Corrupt Database
D. Drake
aa1qd at comcast.net
Mon Feb 18 08:52:01 EST 2008
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
More information about the Dxbase
mailing list