Song Database Issue
 

Help! I upgraded to 3.321 and now I am having problems. I am used to being able to go into the songs database and edit song names, artist, etc. I have been in the process of rating the quality of each song and inputing the ranking in a new column in the songs database. When I upgraded everything seemed fine. But then I realized that the hoster software is no longer using the songs database. I had to reload a couple songs, and they show up in hoster, but do not show up in the songs database. I tried changing the names of a few songs (as was able to doin the previous version) and went back into hoster and the changes I made did not show up. It seems as though hoster is now using a hidden database or something. A databse that has all the songs from the original database I was able to make changes to and have those changes reflect in hoster. What is going on???

Thanks in advance for advice

when did you upgrade to 3.321 and what did you upgrade from?

Because of Vista, MTU moved the location of your database. You probably have 2 copies.

Song Database Issue
 

I beleive it was 3.118 but I am not certain. I have searched my entire laptop but have not found a second database, with the exception of the bucket database, and I do not have access to that database. Is it possible Hoster is working directly with the bucket database now and the songs database is bypassed??

No it uses the Song DB. Rebuild the DB and note to where its putting the db.

Funny thing is
 

the funny thing is I went to import a few extra songs as a test. They imported fine, hoster picks them up and they work fine. I go into the songs database and they are NOT there. Hoster is currently NOT using the songs database it was using prior to the upgrade.

Are you using Access or some other database program to do this editing??

Look in here.
C:\MTU\Hoster

It used to be stored in
C:\Program Files\Micro Technology Unlimited\Hoster
in the older 3.1xx versions, but they had to change that for Vista around the time (or after) 3.118 was released.
They are using the songs.mdb currently.

That is what I was referring to. You are looking at the old database. If the songs aren't in the database, Hoster won't play them. If I was in front of a computer with Hoster right now, I would give you the old vs new path. Can someone help us out here?

edit: Thanks, Lonman. You beat me to it.

access
 

I am using the microsoft Access songs database Hoster originally set up. In the past (before the upgrade) I could correct song names, artist, etc. Before the upgrade I could go into the songs database and make changes, then go into hoster and see the changes. Example: in Hoster I would search by id for "All Summer Long", I would notice the song name would be Aal summer long, a typo was apparant. I would go into the songs database and find the song, correct the typo, then search in hoster and find the record and see it as corrected. Now no new records are importing to the songs database, and If I make any corrections to any records in the songs database, those corrections do not show up in the hoster software. When I added a couple extra songs, they did not even show up in the songs database, however Hoster did find and play them just fine.

Please read the manual Songs Database topic to solve your "misunderstanding" problem. As others have stated, Hoster still uses the Songs.mdb database it builds, but it is now stored in a new location required by Microsoft! :r :)

The world marches on. We document what we change, and Vista FORCED us to change. It is very hard to find a computer today that has Windows XP. NEW computers come with Vista, and have since June 2008. We had no choice. :m

I am VERY GLAD you finally took our advice and stopped using 3.318 as it had a disastrous bug that could cause Windows to delete all your KMA imported files. :e

Any changes you make to songs.mdb are not permanant (not written to the kma file) until the song is pulled up in Hoster's edit song screen and have the changes "applied". I don't know enough about these to know if an added column would also be saved to the kma header.

The 3.318-3.321 period was when MTU was looking for a more Vista tolerant location for some of the files including songs.mdb. When it did this I don't think it copied the old one. I think it re-reread all the KMA's header info and created a new one . That may be why all your changes gone.

Sam

Loneman
 

Loneman, you are the man! Hard to understand how or why a database would be replicated. It looks like I have about 10-15 discs to go back and backfill data on. Now that I think about it, I might just import the few new files from the new database to the old database, then move the old database to the new spot. Either way I now know I am not going insane. Two thumbs up Loneman

Nothing was replicated, like stated, they had to add the separate directory for when trying to make it Vista compliant. The songs.mdb you are used to is an outdated remnant from the previous version no longer used by the current. Chances are if you just copy the old & paste it into the new directory & rebuild your database, you'll have all your updates.

replication
 

It seems as though it replicated the old songs database, and the reason I believe this is I had added a few columns in that old database, (quality, date song was added, Vocals, Comments) and all these columns were in the new database. No worries, I am in the process of squaring one of them up and making sure it goes to the correct folder