>Hi,
>
>we have a database with a number of remote views. The data source is an ODBC connection to an Oracle server - let's call the data source BOPDEV. The clients have setup another Oracle base for testing, let's call the ODBC data source BOPTEST.
>
>What we would like to do is set up two separate environments - one for development (using BOPDEV) and one for testing (using BOPTEST). However, when trying to setup the "testing" environment, merely changing the database connection from BOPDEV to BOPTEST doesn't do any good - the remote views still want to use BOPDEV. The ConnectName property is read-only, and the MODIFY VIEW dialog doesn't allow it to be changed either.
>

You can't change the connection name without destroying and recreating the view, which will cause all of your other view settings to be reset.

But you can preserve all of these settings when changing the connection using eView. You can get eView from here in the files section.