song database

[gd123]

If memory serves, yes, at one time one could type into the Songs Database Destination Folder. I had a hard time figuring what was what in this Menu early on.

2.219 is a very old version where it may be hard to find someone to actually advise properly.

But, really, what does it matter where the Songs.MDB is located other than, it would be quite handy on an external drive that would be used on other computers. For instance, if one wanted to import on one computer and then Import on a different Computer. This would prevent having to synchronize databases/Merging, etc.

Since it can't and if the above is the case, an extra step would be necessary in making sure that the SINGLE Songs.MDB file would work. Just copy it to the external HD after importing and recopy it from the External HD to what ever Computer had Hoster that would be used to PLAY KMAs or IMPORT.

Other than that, I don't see any reason to have the Songs.MDB on an External HD as a "BASE" of operations.

Hoster Terminology 101
Songs.MDB is the DATABASE (The DATABASE is NOT the KMAs)
KMAs are the Songs (KMAs are NOT the Database)

When Songs are IMPORTED, which are converted to KMAs, information about the KMAs are logged in the Songs.MDB "Database," including their LOCATION.

Sometimes, External HDs get assigned a different Drive Letter when connected to a Computer. One could reason that, if the Songs.MDB could be on the same external HD that share the KMAs, then, it wouldn't matter what Drive Letter a Computer assigned.

But it would matter, as the DRIVE LETTER is logged upon IMPORTING.

Even if an operational Songs.MDB could be located on an External HD that was assigned Drive Letter E, Hoster on an alternate Computer would NOT be able to locate and PLAY KMAs if the alternate Computer assigned the External HD Drive Letter D, as the Songs.MDB, located on the External HD, would be telling Hoster that the KMAs were IMPORTED to E and to look for them there.

Join the crowd on the location of the Songs.MDB.

[admin]

Originally Posted by slsides

again, i am in no way confused or wondering about this. the database location could be manually defined. the database files were on the external hdd previously.

Shaun, you are correct. Once upon a time long ago, we had this really creative spurt that we would allow users to create multiple Songs Databases anywhere they wanted.

You could build one for Friday night's show, another for Wednesday nite, etc. limiting which songs appeared and "slowed down" the searches.

Well, folks created Songs Database here there and yonder... and they forgot what they were for. They would open the wrong one, and call MTU all hot and bothered. There is NOTHING we hate more than hot and bothered customers, especially when it was PILOR ERROR that they were suffering from.

It didn't take us long to realize the simple fix was to ONLY allow one Songs Database and to force it to a known location where Hoster could ALWAYS find it. When we released this "functional reduction", we didn't have any complaints... either the loss of fuction or having multiple Databases you didn't understand what they contained. End of problem!

2.219 released 10/20/2004. You're playing with a stacked deck to use that today. PLEASE... upgrade your customer/friend.

Originally Posted by gd123

1. Since it can't and if the above is the case, an extra step would be necessary in making sure that the SINGLE Songs.MDB file would work. Just copy it to the external HD after importing and recopy it from the External HD to what ever Computer had Hoster that would be used to PLAY KMAs or IMPORT.

2. When Songs are IMPORTED, which are converted to KMAs, information about the KMAs are logged in the Songs.MDB "Database," including their LOCATION.

3. Even if an operational Songs.MDB could be located on an External HD that was assigned Drive Letter E, Hoster on an alternate Computer would NOT be able to locate and PLAY KMAs if the alternate Computer assigned the External HD Drive Letter D, as the Songs.MDB, located on the External HD, would be telling Hoster that the KMAs were IMPORTED to E and to look for them there.

1. Good theory, however Hoster is HARD-WIRED to look for the Songs.mdb in a SINGLE location. It cannot be moved and work.

2. Correct! That is why the Tools menu > Build Songs Database dialog requires YOU... the user... to identify where you KMA files are located. If you don't, they won't be in the Songs Database. The full PATH C:\MTU\KMA Files we now use (or the prior C:\Program Files\Micro Technology Unlimited\Hoster\Databases we were forced to discontinue in VISTA - can work in XP/2000 but not recommended) to every KMA files is stored in a field in the Songs Database. That way, Hoster can find and play a song instantly and would NEVER loose where they are, under normal conditions.

3. Correct! If you have a USB DVD drive and an external USB HDD, just plug them in differently one time in the wrong order and poof... neither works and you have to locate the drive and rebuild the Songs Database again.

We have EXTREMELY few users getting confused about where their Database resides. Mostly, it is experts who want to add flexibility we INTENTIONALLY removed, selfishly for our and our reputation's protection.

ENJOY your reliable Hoster program!