Only one MSE Schema can exist in an enterprise GDB

[kgonzago]

Issue - Current Behavior

The add-in continually displays this dialog after I selected an existing enterprise GDB that already has a milsym schema:

Repro Steps

1. Create a new project
2. Create a new DB connection
3. Launch MSE
4. Click on Settings hyperlink. It will prompt you to select flavor of MilSym schema.
5. Browse to newly connected enterprise DB

Note: MilSym schema will be created in enterprise GDB

6. Create new project
7. Click on Settings hyperlink to set MilSym schema flavor
8. Navigate to existing enterprise GDB that has an existing MilSym schema

This is where the above dialog keeps on popping up. MSE add-in "knows" an existing GDB has a schema but for some reason it "thinks" schema doesn't exist.

Workflow Discussion

We have to consider when creating the schema in an enterprise GDB is who "owns" the schema. MSE needs to be intelligent enough to determine that the MilSym schema can be created and owned by various users in an enterprise GDB. This is important in the scenario when MSE prompts a user to navigate to a DB with an existing schema, MSE needs to determine if the schema is available based on the user that's referenced in the DB connection.