Ed, After you sent me the 4 adi files, I did a Standard ADI import into a Virgin database -- bringing all 4 of them in a one time. One after the other - without closing the Non-DXB Import program. Totally perfect with all 349 QSOs accounted for an NO ERRORS.. Initialize Stats worked perfectly.
Then I tried an import of all 4 of them into my own mdb file .. again - perfect action with no errors and again initializing stats was flawless. Since I can not reproduce the problem you saw Ed, I sure don't have any warm feeling abt why it acted up for you when you imported all 4 at one time.. 73 fer nw, Joe WA6AXE Ed K1EP wrote: > I had about four contest (CT adif) logs to import to my DxBase log. I > imported the logs using the utility, one after another, without starting up > DxBase. When I did run DxBase, I found a number of oddities in the log. I > would see several log entry lines that didn't have any QSO data and were > grayed (actually red 50%) out. I saw QSO's that were probably wrong because > they were in the wrong date order, even after sorting. When I tried to do > Initialize Tables, I think I got some non-fatal error, something like > "unrecognized bookmark". Initialize Tables only found about 10% of the QSO's > in the log. I thought maybe I did something funny, so I reverted back to my > saved log (Yes, I made a copy before doing all this). I carefully did the > same import process again, importing the logs in a different order. Same > results. I then imported the logs one at a time on the original .MDB file, > running DxBase between each import to verify that the import went okay. By > doing that, the log was fine after the four imports. When I looked at the two files, the bad .MDB file was something like 10% larger in size than the correct log after the imports. Is there anything in DxBase that requires you to run DxBase after an import?? I am pretty sure that I have done multiple imports in the past without any problems like this. Anyone see similar results? > > ______________________________________________________________ > Dxbase mailing list > Home: http://mailman.qth.net/mailman/listinfo/dxbase > Help: http://mailman.qth.net/mmfaq.htm > Post: mailto:[email protected] > From [EMAIL PROTECTED] Mon Jul 18 12:52:04 2005 From: [EMAIL PROTECTED] (Ed K1EP) Date: Mon Jul 18 13:04:48 2005 Subject: [Dxbase] ADIF import to DxBase2006 problems - UPDATE Message-ID: <[EMAIL PROTECTED]> I was able to run the REPAIR utility on the damaged file that was produced after the imports with apparent success. I was also able to COMPACT the original database and then import the files with no problem. I am not exactly sure why the import failed, but I have been able to successfully import the logs one at a time or all at once on a compacted database. So, I guess if you do run in to a problem, try compacting the database first. >I had about four contest (CT adif) logs to import to my DxBase log. I >imported the logs using the utility, one after another, without starting up >DxBase. When I did run DxBase, I found a number of oddities in the log. I >would see several log entry lines that didn't have any QSO data and were >grayed (actually red 50%) out. I saw QSO's that were probably wrong because >they were in the wrong date order, even after sorting. When I tried to do >Initialize Tables, I think I got some non-fatal error, something like >"unrecognized bookmark". Initialize Tables only found about 10% of the QSO's >in the log. I thought maybe I did something funny, so I reverted back to my >saved log (Yes, I made a copy before doing all this). I carefully did the >same import process again, importing the logs in a different order. Same >results. I then imported the logs one at a time on the original .MDB file, >running DxBase between each import to verify that the import went okay. By >doing that, the log was fine after the four imports. When I looked at the two >files, the bad .MDB file was something like 10% larger in size than the >correct log after the imports. Is there anything in DxBase that requires you >to run DxBase after an import?? I am pretty sure that I have done multiple >imports in the past without any problems like this. Anyone see similar >results?
