Guess i'm not understanding that. It will change a duplicate book id but not merge into the database?
What i'm saying is it didn't change the book id number, but merged it into the database with the same book id number as one that was already there. So I now have say 2 songs that I can actively search with 1 book id, they will both come up as each title but if I click the ones that I want, it will bring up the original.
Example in the attachment...well actually the problem of one of the discs I am talking about. The KAR006 disc is the new one. It comes up in the search, but had the same book id as the Star Disc. Now when I rebuilt the database, it didn't add the new disc to the database, but gave me the duplicate book id message & logged it. So I did the merge command as it is supposed to change that book id to a useable number, instead it just added the disc to the database with the same book id number instead of changing it.
It did this with several other discs I just got as well. I know it's my bad for using a separate computer to import with, but I figured it would work out anyway if the duplicate book id would be renumbered instead of just adding it to the database & not being able to use it anyway.
Last edited by TTowntenor; April 19th, 2008 at 05:30 PM.
Reason: redid attachment
|