I have been successfully using MC9 with a database of about 60,000 tracks and it is wonderfully stable. I use several external USB2 drives (250GB) and the drives move from machine to machine where its assigned drive letter, unless specifically set, will be variable based on the PC's local resources.
I keep the Media Center data folder on the same volume with its content. I then copy 'browser.jmd' around to share database views (sometimes). However, the database keeps a hard pointer in 'mediafiles.jmd' which includes the drive letter to the media file, of course. This is good if one has just one PC and maintains a central database but if the database is portable on an external drive then this is problematic. To maintain some sanity, I change drive letters on the external drives to 'M' so that the external drive works on all of my machines but I then cannot have two drives together and both open in MC9.
Question: if after more than a year working with your fine program and I somehow have overlooked something, my apologies in advance. Otherwise, is there any way to have relative addressing where the database 'mediafiles.jmd' assumes its media files are relative to that volume's root (or relative to its current path)? Could there be an option that could turn this notion of relative volume addressing on or off?
This would go a long way to making MC9 almost perfect (field auto-completion for in-line editing and you will have absolutely achieved perfection).
Great work, I continue to be amazed...
Author
Topic: Database Portability Sanity (Request for...) (Read 887 times)