And windows determine which instance it will return we have never found the way to control it.

[quote="Peke"]Hi,
You can get iDispatch address from MMW internal Script start so that access works even on MMW portable.[/quote]

I just noticed this.

I am sorry. I don't understand.

In a Python context, I do the following (from docs)

SDB = win32com.client.Dispatch("SongsDB.SDBApplication")

How do I apply your advice?

Hi,
You can get iDispatch address from MMW internal Script start so that access works even on MMW portable.

[quote]If I had a 2nd version of MM running how would I connect to the correct instance?[/quote]

ALSO INTERESTED.

I experimented for 2/3 days with such a pursuit and concluded its not gonna happen without major experimental hacking of installation registry files. I'd love it if someone can share/reveal a clean method to use multiple MM windows through scripting or command line.

[quote="rivorson"]One thing you might change is allowing multiple instances of MM so you wouldn't need to close the instance running your production database before opening the instance with your test database.[/quote]

Thanks.

My COM knowledge doesn't extend much beyond the supplied MediaMonkey documentation. I am just following the advice showing how to establish a connection using Python, ie.
SDB = win32com.client.Dispatch("SongsDB.SDBApplication")

If I had a 2nd version of MM running how would I connect to the correct instance?

Running a VM is always a good option but I think you've got the right approach. One thing you might change is allowing multiple instances of MM so you wouldn't need to close the instance running your production database before opening the instance with your test database.

The option is Tools --> Options --> General --> Allow just one instance of MediaMonkey.

[quote="Peke"]Have you tried to install MMW as Service?[/quote]
No.
Could you explain how that would help me?

I want to:
* use MM normally, with it pointing to my production database
* but when testing the COM app, I want that test run to be updating my test MM.db

My workaround, is to:
* close down MM prior to the test
* restart MM using a command line, which overrides to a testing ini file, pointing to the test MM.db
* test the COM application ... it uses the running invocation, ie. the test MM.db
* close down MM after the test, and then restart MM with the regular ini file

I was just wondering if there was something more idiot-proof.

Are you meaning that I can get the COM connection to attach to a testing secondary MM invocation?
something other than SDB = win32com.client.Dispatch("SongsDB.SDBApplication")?
How would I start|name this secondary invocation, and how would I get it to use a testing ini file?


Maybe it would be best to do my testing inside a VM?

Hi,
Have you tried to install MMW as Service?

a workaround is to try to remember to pre-start MM with a inifile override on the command line.

I am testing an external (python) application using MM automation objects.

ie. SDB = win32com.client.Dispatch("SongsDB.SDBApplication")

If MM is not already running, it is invoked, and its database is pointed at my production MM database, as per the MediaMonkey.ini found at C:\Users\xxxx\AppData\Roaming\MediaMonkey

Is there a way to override which inifile is used, so that I can point it at a test MM database?