Build Song Database Locks up Laptop

[SteveD]

The build song database keeps locking up my laptop after adding in excess of 10,000 songs. Sometimes it makes it to 18,000 and then it locks up the computer. I have 28,500 songs total and the laptop is using Hoster 3.303.

I have tried deleting the songs.mdb file and still no luck. I would update hoster but I can't access my store account as I can't retrieve my password with the current email account on file. This is another issue that I can't seem to get resolved.

To say I am dissapointed with MTU would be a serious understatement. They used to answer a telephone. I need this system working for a Saturday night show and have been trying to access my store account since Friday. Yes I have submitted a ticket.

[mindonstrike]

Any error messages?
Any errors showing up in the event viewer?

Just speculation but possibly Hoster is running into a corrupt KMA header or possibly a header with a song title or artist name that is larger than the database field.

As a possible workaround you could try and divy up the KMA files to say 3 folders with 10,000 each, import the first folder and then use the merge funtion to import the other two folders (one at a time).
If it consistantly locks up on a particular folder I would suspect a problem with a particular KMA in that folder.

Sam

[SteveD]

It is completely random about what number of files processed that it locks up on. But I will try divying them up to three separate folders.

[gd123]

You can build your SONGS DB on A N Y Computer that works and has Hoster Installed.

If it makes it through the Rebuild, transfer the Songs.MDB to your Laptop.

This will help in determining if you have a problem with your Laptop or your KMAs.

Another thing. If you haven't already done so, and, because you mentioned that you have tried deleting the Songs.MDB, you will notice that, upon running Hoster for the 1st time after deleting the Songs.MDB, Hoster will try to REBUILD the DB on its own. Once the Process starts, CANCEL the REBUILD PROCESS and let Hoster OPEN. Then, do the REBUILD from within Hoster. See if that makes a difference.

If you use Printed Songlists where the BOOKID is listed as the SOLE REFERENCE for you Singers to find a SONG. I, definitely, would NOT have Hoster renumber my BookIDs. This will render your Songlists useless.

If you have the resources, Backup ALL your KMAs, then try the renumber thing. May take several Days to figure out if all your KMAs work/same BOOKID. And, if not what you expected, you have the UNCHANGED Backups.

[SteveD]

I have already tried tranferring the songs db over to the laptop but the paths are different since I use an external hard drive on the laptop. I have also just ran the rebuild song database on another machine and it runs without any problem.

I have five systems total so songnumbers are critical to stay the same. Not all the song librarys are the same but most of them are and I am not experiencing this problem with any other system.

I think it is a quirk with my current version of hoster on the laptop. I would update it but I am locked out of my MTU store account! I have been trying to get someone at MTU to look into this for me to no avail. Apparently my new password is being sent to an email account I no longer use.

I really do appreciate the time you have taken to respond to this post. You have given me some good new tricks to try and resolve this issue.

[gd123]

Take the External Drive that you are using on the Laptop, which won't build right, and hook it to any other Computer.

When the Computer assigns a Drive Letter, change the Drive Letter to what your Laptop uses.

Build the DB.

Transfer the newly built Songs.MDB to the Laptop.

Now, the Drive letter in the Songs.Mdb will point to the correct External HD Path.

Or, you could disregard any Drive Letter that is assigned, by the Computer you are using to build your DB, and EDIT the Songs.MDB's Drive Letter, with MSAccess, to match what your Laptop uses.

MfgName	DiskID	Track	Duration	SongTitle	Artist	Path X	BookID	Language	Genre	Duet	Multiplex	RecordID	Type

Edit the PATH Column and REPLACE THE DRIVE Letter:
< Current Drive Letter>
with

ex:
D:\MTU\1\DK098-16.kma
I:\MTU\1\DK098-16.kma

In the FIND field, use: D:\ <---whatever your Letter is
In the REPLACE field, use: I:\ <----To whatever you need it to be

In the MATCH field, use: START OF FIELD

[SteveD]

I will give this a try, don't see any reason it won't work. Thanks,

[ddouglass]

Originally Posted by gd123

Take the External Drive that you are using on the Laptop, which won't build right, and hook it to any other Computer.

When the Computer assigns a Drive Letter, change the Drive Letter to what your Laptop uses.

Build the DB.

Transfer the newly built Songs.MDB to the Laptop.

Now, the Drive letter in the Songs.Mdb will point to the correct External HD Path.

Or, you could disregard any Drive Letter that is assigned, by the Computer you are using to build your DB, and EDIT the Songs.MDB's Drive Letter, with MSAccess, to match what your Laptop uses.

Edit the PATH Column and REPLACE THE DRIVE Letter:
< Current Drive Letter>
with

ex:
D:\MTU\1\DK098-16.kma
I:\MTU\1\DK098-16.kma

In the FIND field, use: D:\ <---whatever your Letter is
In the REPLACE field, use: I:\ <----To whatever you need it to be

In the MATCH field, use: START OF FIELD

GD123, I like your method with MSAccess, but you might want to point out for them NOT to convert the db when open it in newer versions of MSAccess.