Quote:
Originally Posted by ddouglass
Sounds like it is time for them to upgrade as well.  Upgrade is a whole lot less than buying new.
Anyway if that is what you did then the Merge KMA files should fix it. |
thanks, your advice was spot on.
i also found that if i manually hex edited the .kma files, i could set the bookID correctly that way, but merging the db was, of course, much faster.
oddly, once the merge was complete, i got a new log file with this header:
DUPLICATE KMA FILES (same discID and track#) DETECTED DURING DB MERGE
but when i reference any of them, there are no duplicates. so i'm not exactly sure what the deal is there.
thanks,
shaun
edit: we've discussed doing the upgrade to 4.x. one of them is barely computer savvy enough to manage as it is, so more complex software isn't really of interest to him. the other one is interested in doing it, and may at some point. obviously, any new customers i develop will automatically be 4.x users