BuildSongDBLog.txt WRONG

[Skybird74]

I have just rebuilt my database for the first time after installing 4.03 on XP. It told me I had 2,000 duplicate IDs. After looking at the list, I noticed that most of these songs appeared on a prior list, which was corrected some time ago.

Also, these entries are not consistent. In some cases, when I pull up the Dup.ID#, it is true that there is a different song assigned to this number, and therefore I need to re-import the song that was not added to the database.

However, in some cases, the Dup.ID# is still in the database as the exact same song, i.e. ID41412 was listed as a Dup. song. But when I pulled it up, 41412 is exactly the same song with the same Disk ID, which means I do NOT have to re-imort this song because it is still there and it plays fine.

In a completely different case - one of the DupID songs that is NOT supposed to be there, IS there but it will only play the Audio and not the graphics.

This means to me that I would have to go through all 2,000 songs 1 by 1 to see which ones DO or DO NOT need importing. This is very upsetting.

[bryant]

Originally Posted by Skybird74

I have just rebuilt my database for the first time after installing 4.03 on XP. It told me I had 2,000 duplicate IDs. After looking at the list, I noticed that most of these songs appeared on a prior list, which was corrected some time ago.

Also, these entries are not consistent. In some cases, when I pull up the Dup.ID#, it is true that there is a different song assigned to this number, and therefore I need to re-import the song that was not added to the database.

However, in some cases, the Dup.ID# is still in the database as the exact same song, i.e. ID41412 was listed as a Dup. song. But when I pulled it up, 41412 is exactly the same song with the same Disk ID, which means I do NOT have to re-imort this song because it is still there and it plays fine.

In a completely different case - one of the DupID songs that is NOT supposed to be there, IS there but it will only play the Audio and not the graphics.

This means to me that I would have to go through all 2,000 songs 1 by 1 to see which ones DO or DO NOT need importing. This is very upsetting.

Something like this happened to me a few days ago when I was working with only 900 files, not sure what it was so I deleted all the song database and song.backup database and reimported those songs using Hoster 3.4, and the database straightened itself out. This was easy for me to do as it wasn't a show machine, sort of a practice test machine, so I could afford to mess with the database. I'm not sure if this is what is going on in your case or if I am of any help, but database things apparently are happening on other computers.

[Skybird74]

OK, here's what I did. I deleted the songs.mdb and songs_back.mdb. I ALSO deleted those same "oldler" files from under "ProgramFiles/Hoster". Then, I rebuilt the database. Not only did the .mdb go from 1,976KB to 3,824KB, but I didn't even get a message regarding "BuildSongDBlog". In fact, I didn't get any messages about duplicates or anything else

[Skybird74]

I think I spoke too soon.

Here's what happened:
New 1st time install (did not delete old .mdb from Program files)
Building database said: 12,684 files, leaving 10,824 songs (1,976KB)
(received dup ID message)
Where did 43 files go?
Deleted prior .mdb and .mdb from Program Files
Restarted Hoster, it started Building automatically:
Now it said there were only 12,641 files, but only 10,751 songs (3,824KB)
(did not receive any message about there being any dupes)

Before anyone asks, NO, I DIDN'T ADD, DELETE OR EVEN PLAY ANY SONGS, so there is NO REASON that the number of files I began with should be any different.