Well, what if you change the DBName entry before you start MM? This way, you can make a workaround that you can use until the dev's have some other way of doing it. This can be done by a very simple program. I just tried it myself (.Net unfortunately).Perhaps, as a 1st step, the developers could add a command line option to specify the starting DB (overriding the possible "DBName" option from the .ini). Hence you could create a shortcut for each MM "configuration":
- mediamonkey.exe /DB "c:/my docs/music/mediamonkey.mdb"
- mediamonkey.exe /DB "c:/my docs/soundtracks/mediamonkey.mdb"
- etc
If this doesn't come in MM2.5, then maybe someone can program something similar in a Microsoft VS6 language or assembler.
Code: Select all
using System;
using System.Runtime.InteropServices;
using System.IO;
namespace ConsoleApplication3
{
class Class1
{
[STAThread]
static void Main(string[] args)
{
if(args.Length == 0 || args[0] == "/?"){
Console.WriteLine("Usage: <Program> \"INI location\" \"DB location\"");
}else{
WritePrivateProfileString("System", "DBName", args[1],args[0]);
}
}
[DllImport ("Kernel32")]
public static extern bool WritePrivateProfileString(string lpAppName, string lpKeyName, string lpString, string lpFileName);
}
}Cheers
Steegy
