building kma database

[dallaspaul]

I have a similar issue with space. I notice that BookID is a THREE character field, thus I assume limited to 001 to 999 inclusive. When I import disks via hoster, whether by single or batch, it changes BookID as the source disks change, which is logical, as the track number of each disk begin with 1 (one). The hoster program instruction manual states that track numbers are two digits, meaning 01 to 99 inclusive.

My question: Is there a method/manner/program in which the KMA files can be renumbered, so that the remaining tracks (eg.: on a 8+8 disk, where only 8 performance tracks are imported, meaning upwards of 92 tracks are wasted) can be utilized per each BookID?

OR
Is there a method/manner/program that can utilize more that one database at a time while running HOSTER?
While most of my original disks contain 14 to 30 tracks, with 15 being most common, I realized that the result would be that I could have as few as 8,000 songs to a maximum (using the common 15 tracks per disk) of 15,000 songs. Not good. I still have 600 disks to import....