My initial installation was for personal use with a local data source. We then began evaluating the enterprise version configured with a SQL Server data source. I have both data sources configured, one contains personal info the other corporate info. Access to the local data source is with a master key and access to the SQL Server data source is via windows authentication. Since both data sources are configured, on launch the program always prompts to enter the master key.
Here is the issue... when the program is minimized and requires re-authentication, it askes for database credentials, not the Master Key (see attachment). None of our users will ever have the database password, since Windows Authentication is used.
The only work-around that I have found is to kill the PMV process in the task manager and relaunch it. BTW, v4.1.0.0 is installed.
edited by dougk on 5/7/2013
Here is the issue... when the program is minimized and requires re-authentication, it askes for database credentials, not the Master Key (see attachment). None of our users will ever have the database password, since Windows Authentication is used.
The only work-around that I have found is to kill the PMV process in the task manager and relaunch it. BTW, v4.1.0.0 is installed.
edited by dougk on 5/7/2013