Removing/reimporting

[bubba1453]

My partner was importing a recently purchased Sound Choice Disk
2218. When he imported, he somehow utilized 22118 as the Book Id#. It should have been 383,tracks 1-8. He tried to remove the imports and import again to correct the Book Id. It will not let us remove the file and correct the ID information. Any help will be appreciated.

Thanks everyone
Bob

[gduns - with the Lord]

You might try moving songs.mdb from the databases directory and do a songbook rebuild after you remove the kma files from your directory. I think it would do the trick for you. if you didnt like the results you could always put the songs .mdb file back and you would be back where you started.

[mindonstrike]

I have the same problem .
I deleted the incorrectly imported songs and reimported with the correct bookid and rebuilt the song database, but when I add one of those songs to my playlist using the "song" tab it still recognises the old book id, which of course gets me a can't find song error. I can't add those songs without using the bookid tab with the new (correct) bookid.
I read somewhere on here you can fix this by going into the database with Access but I don't have that program.

Sam

[mindonstrike]

I just noticed gduns suggestion to move song.mdb before rebuilding. I'll give that a try also.

[MTUSUPPORT]

Gduns is correct, this is how you should do this. I think this is explained in the manual.

[DJMonty]

I've just bought the latest Hoster (version 2.0)

I imported a discs then realise I'd made mistakes, so I deleted the .kma files and song.mdb then rebuilt the database but it still has the deleted tracks etc in the hd listings. Is there a way of clearing everything and starting from scratch. I tried uninstalling and reinstalling but it still had the deleted track listings.

[mindonstrike]

You can rebuild your database until you are blue in the face but if the "select folder" is not set to where Hoster looks for "songs.mdb" you will see no change, and if you move songs.mdb Hoster will show that you have no songs. If you forgot where you moved it from or deleted it you will have problems.
If there is a way to tell hoster where to look other than it's default location, I haven't found it yet (and I have studied the manual)

solution: find where hoster originally placed your songs.mdb (hoster\databases\ I think ) and make sure that "select folder is set to that path or rebuild it to an easy to find spot such as C:\ and then copy and paste it to it's correct location.

If you did something stupid like I did and moved songs.mdb along with the backup to another location and forget where it came from, try importing a
single song - which will cause Hoster to create a new songs.mdb, and then do a search in explorer for that file. By noting the time you imported it and the fact that it is an extremely small file you can be sure thats the location where you need to rebuild your new database.

I hope this helps.
Sam

[mindonstrike]

I would bet that after deleting the KMA files you first rebuilt the database, discovered it didn't eliminate the songs you wanted to eliminate and then tried deleteing the database and tried again.
The fact that you could delete songs.mdb
and Hoster can still see it means that hoster is looking at a songs.mdb in a location from which you didn't delete, if you can find that location, again searching with explorer if need be, then you should be able to rebuild your database there.

Again I hope this helps.
Sam

[DJMonty]

Sam your a superstar, that worked and I'm back on course

[mindonstrike]

I'm usually on the recieving end of computer related help.
It's nice being on the giving end for once!

Glad I could help.
Sam

[admin]

The "Select Folder" field SHOULD globally change where Hoster looks for the songs.mdb database. Regretfully, because of a bug, it doesn't. That is why just rebuiding the Songs database doesn't behave as expected.

This is the first bug that will be repaired when our programmer returns this Sunday (give him a few days to find and fix it and for us to test it). Then, we'll release 2.015 with that bug fixed. It's bad enough to justify a separate release just for that.

[mindonstrike]

I would think an email to customers detailing the problem and solution along with a note on the forum would be sufficient for now. IMHO.

Sam

[DJMonty]

Similar Problem:

I'm now well on my way to transferring my discs. I've accidently put a duplicate track on, I deleted the track from my hard drive then built song data base, but the track still appears in the playlist even though if you try to add track to the playlist a message comes up track was not found on hard drive. What am I doing wrong.

I've even tried deleting all .mdb but this didnt work either. When will the above upgrade be ready as that sounds lkie it will stop these errors?

[pcgumshoe]

I know of this problem and, albeit, a new release of MTU programs is ALWAYS welcomed, the work around is rather simple. Whenever you have had a problem just remember, if Windows is always looking for the program software in the folder c:\Windows and you move the program files to c:\Programs unless you tell Windows to look in the new place, it won't. It will ALWAYS use the old files until you change it.

As I don't program, and I don't work for MTU I have NO CLUE how to re-program the software for where to look... THEREFORE, if I always install what I need to where it should go (avoids this bug). Whenever you delete (or need to delete something) delete the mdb file from c:\Program Files\MTU\Hoster\Databases. Then AFTER you have deleted all the tracks and reimported all the tracks you want, rebuild the database and make sure you save the database to the SAME place above.... It should ALWAYS work.

IF you don't save the NEW mdb in the right place I THINK that MTU has a back-up of the last saved file somewhere and it reverts back to this. So, make sure that the file is stored where it needs to be.

Hope this helps

[mindonstrike]

The same fix that I outlined above should work here as well except you may have to delete songs.mdb to get it to work.

I had this same problem saturday, I had a couple of dupes that were being a pain in the backside because hoster always pulled them up by default when I'd use the song tab. Like you I deleted them from songlist and rebuilt but they were still in the database. I had to delete songs.mdb to force it to rebuild with only what was in the songlist folder.
Hoster is good at adding new info but not at subtracting obsolete info.

On this next part I'm guessing but better safe than sorry.
when you rebuild songs.mdb the first thing hoster does is create a backup. I'm guessing that if you've deleted songs.mdb there will be nothing to backup and you might end up with a backup file that is empty. So for peace of mind you might want to change the name to backup1 or something so hoster can't overwrite the file.
Both songs.mdb and the backup are located in the same folder.
And of course you can always restore the deleted file from the recycle bin


Hope this helps.
Sam