Hello Brian Goldman,
Let me clarify a bit the way OpenAccess works with connection strings. As you can see in the <openaccess> configuration node, there are several <connection> nodes that map each connection string to a backend-specific configuration. This is required as particular database backend (for instance MSSQL) could have settings or field/column mappings that are not relevant to another backend (like MySql). Having this in mind, if during deployment you change a connection string that was initially used obtain a mssql connection to connect to a mysql server, this would most probably lead to runtime errors as the new mysql connection string will use the old mssql backend configuration.
To avoid such behavior it would be best if you do not change the connection strings but use an additional custom configuration node (for example <activeConnection name="connectionStringName" />) that you can read and use at runtime to determine which connection should be used. Note that you can still change the server and database names according to the deployment machine, just keep the backend that the connection string was initially defined for.
When you already know which connection string should be used, there are two possible approaches. You can either call the Database.Get() method with the appropriate connection string name as you pointed in your last post or create an additional ObjectScopeProvider for each connection string. It is up to you to decide which method to use, they will both work. Hope that helps.
All the best,
the Telerik team