#2467 Force Keepass to open Database in new Tab or new Instance for cmd://

[bentron]

I have two different Keepass folders:
Keepass1 and Keepass2 (both portable versions)
I want to manage them separately, because they have different Settings / Plugins etc. I have problems by opening them in same instance or open in a complete new instance.

I am searching for a workaround but inspecially when two different instances (Keepass1 and Keepass2) are running at the same time, the recognition how to open files gets changed. As workaround I have disabled the option (Limit to single instance) but on some situation I can not open e.g. Keepass1 if Keepass2 is already running. But I want to open Database1 only with Keepass1. And all other Databeses with Keepass2 in tabs.

I have noticed, that Triggers and also KeeAutoExec will open new Databeses always in new tab however the "Limit to single instance" option is confirgured.

It would be great, if there is a option to force open in tab or in new instance inspecially for the URL cmd:// option:
cmd://"{APPDIR}\KeePass.exe" "{APPDIR}\Files\DatabaseA.kdbx" -pw-enc:"{PASSWORD_ENC}"
possible to add new optioin here ???: ( -opennewinstance) or ( -opennewtab)

[wellread1]

As workaround I have disabled the option (Limit to single instance) but on some situation I can not open e.g. Keepass1 if Keepass2 is already running.

the "limit to single instance" option must be set for both KeePass installations. Based on the above statement it is probably still checked for "KeePass2".

[bentron]

This will not work. I show you why:

-Step1-
DatabaseA is opened with Keepass1
And one entry of that shows followed URL field:
cmd://"{APPDIR_Keepass2}\KeePass.exe" "{.......\Files\DatabaseB.kdbx" -pw-enc:"{PASSWORD_ENC}"
This command will open DatabaseB with Keepass2 only if Keepass2 is not limited to single instance!

-Step2-
Now DatabaseB is opened with Keepass2, and there an URL entry shows:
cmd://"{APPDIR_Keepass2}\KeePass.exe" "{.......\Files\DatabaseC.kdbx" -pw-enc:"{PASSWORD_ENC}"
This will open DatabaseC with Keepass2 in new instance, because limiting to single instance is not possible (remember Step1). I have no chance to open DatabaseC with Keepass2 in new tab.

If Keepass1 is limited to single instance and Keepass2 is not limited, you can not run Keepass1 if Keepass2 is already running. :-)
Only way to run both in this contellation is, to open Keepass1 first and after then open Keepass2. If both instances are limited to one instance, you can not open both instances simultaneously.

Thats why I'm missing the feature to force open in new tab or new instance with something like a new option ( .....\Files\DatabaseB.kdbx" "-opennewinstance" or "-opennewtab"

Remember: Triggers and also KeeAutoExec will open new Databeses always in new tab however the "Limit to single instance" option is configured. That means, there is a mechanism already working behind. Only need to get control of it. It is an everytime workaround to configure Triggers (Buttons) to force open new (Databases C, E, F,G... ) in tab.

[wellread1]

You have three databases DatabaseA, DatabaseB, and DatabaseC. You want to open DatabaseA and DatabaseB in different KeePass instances. You want to open DatabaseC in the instance containing DatabaseB.

1. Associate a KeePass installation with the .kdbx file extension, e.g., Tools>Options>Integration(tab)>Create Association(button).
2. Assuming DatabaseC is on your desktop, set the URL field of the entry that is used to open DatabaseC to %USERPROFILE\Desktop\DatabaseC.kdbx.

When you double click on the URL field above, DatabaseC will open in a new tab of the current KeePass instance even if Limit to single instance is not checked.

[Paul]

If you want the database to open in a new tab with the password supplied, use this trigger:
https://keepass.info/help/kb/trigger_examples.html#openod

cheers, Paul

[bentron]

thanks for feedback guys.

to: wellread1
it is not working. I have tried like you prefere the config. In Keepass2 it opens second instance.
the cmd command are different. One is for keepass1 and the other is for keepass2. The strange thing is, that cmd://keepass1.exe forces open the database1 in new tab of keepass2. Video timestamp: 0:45

Please watch the video:
https://drive.google.com/open?id=12gl6LYaXYHImLWewBfrP9FB_hyCZxY3U

to: Paul:
I know that (as you can see in my first two posts) but it is huge work to configure 10 Steps for any new Database.

[wellread1]

The video at 0.45 sec is curious. I am not able to reproduce the results. It is possible that the behavior is being caused by un-noticed changes to the config files of the respective KeePass installations. You might also try rebooting your computer then verifying the test.

Your mixed mode configuration is complex (the instances have to be started in a certain order) and I doubt it is stable. KeePass expects to run in one mode, either single-instance mode or multi-instance mode.

KeeAutoExec does a good job managing multiple databases. Especially if you expire auto-open entries. Expired auto-open entries are added to the KeePass menu at File>Open (KeeAutoExec) but they are not open automatically. When the user selects an opened database from Open (KeeAutoExec) menu, the database is opened in the current workspace. Opening less used databases this way is very convenient. KeePass in single instance mode simplifies configuration and use, but if you prefer you can use KeePass in multi-instance mode.

When you use cmd:// in the URL field you are executing a command line. So the feature request is effectively a request for a command line option. While context appears obvious when a command line is run from the URL field (or a trigger or plugin command is run) it may not be so obvious when a command line is executed from an arbitrary location.

[bentron]

yes it is a feature request for the command line option.
( .....\Files\DatabaseB.kdbx" "-opennewinstance" or "-opennewtab"
...or something similar as option. So the user can decide how (or where) to open the database.