I forgot to mention the worse part of this problem. It replaces the personal options back to the virgin database data. BTW I did set my original log database as the target and the imported database as the source as evident by the number of QSOs imported. I like Jack but I don't want his personal data cluttering up my log database :)
73, Art W2NRA ----- Original Message ----- From: "Art Searle W2NRA" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, May 31, 2004 2:46 PM Subject: [Dxbase] DXB Import Problem > I think I've discovered an possible error in the > DXbase import routine (the .mdb import not the > non-DBB import). This import routine seems to > import more than just QSO even if that's the only > box you check. > > Here is what I did when attempting to import my > weekend contest log: > 1) I imported the contest log into a virgin DXB > file. I did this so I could review it before > importing into my master log. > > 2) I then imported only the QSOs into my master > log. I did index the source file before > importing. I got the following error: > > "The changes you requested to the table were not > successful because they would create duplicate > values in the index, primary key, or relationship. > Change the data in the field or fields that > contain duplicate data, remove the index, or > redefine the index to permit duplicate entries and > try again.AA4LU" > > Again the AA4LU was deleted from both target and > source files prior to import. So, is there the > DXB import file? My database, is it corrupted? > > I finally did a direct non-DXB import and that > worked fine. > > BTW the above incident is an argument for > maintaining multiple backups. Had I only gone > back one backup I'd have been out of luck. > > 73, > > Art > W2NRA > > > _______________________________________________ > Dxbase mailing list > [email protected] > http://mailman.qth.net/mailman/listinfo/dxbase >
