Page 1 of 1

3.0.0.1074: Database Conversion Issues (Redux)

Posted: Wed Sep 12, 2007 10:39 pm
by Mizery_Made
Glad to see the conversion process was greatly improved, looks like all the problems I noted for the previous beta HAVE been cured. Though, I have noticed three new problems, two are missing data and a third is just a 'WTF' Lol. Seems both the Publisher & Lyricist fields are eaten in conversion. Not a one of my files had this data in the converted database, functions fine with a fresh database.

The third involves the 'Original Year' field. I don't use this field often, but I do have one album that's a compilation which had released/recorded years supplied for each track, and I have that year stored within this field. None of my other files have this, and the one album that does has values ranging from about 1996-2005. In the conversion database, you go to the first track of this album, which has the value of 1996, and all is fine. The problem comes with everything in the database after this file. I mean EVERYTHING. Not just the files from this album, the one with these values. It has taken the first found value for this field (1996) and placed it in the field for EVERY song stored after this one within the database, even overwriting those that has other years (1997-2005) Hope that one makes sense.

Anyway, glad to see things moving along, can't wait until MM3 is bundled nicely with a bow saying 'Final Release.' Keep up the great work guys. :)

Re: 3.0.0.1074: Database Conversion Issues (Redux)

Posted: Thu Sep 13, 2007 6:18 am
by PetrCBR
Thanks. Will be fixed.

any way to open mm.db in access or other program

Posted: Fri Sep 28, 2007 11:01 pm
by jamey
Is there any way to open the database like we could with version 2 in access or some other program?