My suggestion to this import is, that if importing source and destination is same version, import program should ask before importing personal data. This would evade this problem, that I have heard many times before. There are many reason to import where source and destination is same version.
73 de ?ystein Stokkeland LA7QI Tel: +47 51 67 70 97 / +47 971 56 090 email: [EMAIL PROTECTED] *****Representant i Norge for DXbase logging program***** -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Art Searle W2NRA Sent: 01. juni 2004 04:50 To: Jack; [email protected] Subject: Re: [Dxbase] DXB Import Problem Hi Jack, Sounds logical. Except why is there a section called "Data to be imported" and it has boxes to check to include what you want to import? Also why would you want to overwrite basic personal data with an import? At the very least I think this might be a revision for DXB2006. I know that I could have imported the adi file directly and that is what I eventually did. But I wanted to experiment with the import to try some search and replaces some of the data to get it to import information I wanted. At your suggestion I tried creating my own virgin data base. I deleted all of my QSOs except the first one. I changed the date on that one and marked in invalid and then indexed. I still got 17 index errors as follows: "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.[each of 17 different callsigns were here]" Art ----- Original Message ----- From: "Jack" <[EMAIL PROTECTED]> To: "Art Searle W2NRA" <[EMAIL PROTECTED]>; <[email protected]> Sent: Monday, May 31, 2004 4:25 PM Subject: Re: [Dxbase] DXB Import Problem > Art, > > There is a much simpler and more logical explanation: > > 1. You created an empty database. > 2. By default an empty database contains default user info in it which you > are expected to change to your own data, but you didn't do that. > 3. You imported into this empty database, reviewed it, but didn't change > any of the personal option default data. > 4. Then, you treated this as a source database and imported it into your > master. > 5. As a result, the default personal data overwrote what was in your > master. > > A better approach would have been one of the following: > 1. Import the contest database into your master instead of the intermediate > step you took. > 2. If you want to use the intermediate step, then you have to fix up the > personal options else you get the defaults. > > Cheers, > Jack > > ----- Original Message ----- > From: "Art Searle W2NRA" <[EMAIL PROTECTED]> > To: "Art Searle W2NRA" <[EMAIL PROTECTED]>; <[email protected]> > Sent: Monday, May 31, 2004 3:50 PM > Subject: Re: [Dxbase] DXB Import Problem > > > > 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 > > > > > > > > > _______________________________________________ > > Dxbase mailing list > > [email protected] > > http://mailman.qth.net/mailman/listinfo/dxbase > > > _______________________________________________ Dxbase mailing list [email protected] http://mailman.qth.net/mailman/listinfo/dxbase
