Yet another reason why RV's suck....<s>

Properties like ConnectHandle, connection ,SQL, etc.. are all read only. If you must use a RV, you best bet is to take a template approach. Bascially, you create a dbc with some basic view defs. In the DBC, you would have your various connection objects defined. When you need to actually connect to a data source, you use the meta data in the DBC, and the specific connection object info to create a local DBC with associated SQL-Views on the fly. Because you are using RV's, you are hamstrung by VFP's meta-data storage requirements. They are not dynamic, mostly becuase the DBC is shareable. You can create a dynamic environment by creating your own DBC on the fly....

>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.
>
>So the question is: is there a way to alter the connectname for a remote view without deleting and recreating it? (we have a good number of remote views). We would also like to avoid just changing the database in the ODBC source (by going to ODBC admin) since there is the chance of forgetting to change it back as we switch environments.
>
>Any help is greatly appreciated!
>
>thanks,
>Michel