>The current connections that I have to my remote views are pointed to sQl server which I will later use as production. I just recently borught up a new sql server to be used as my test server. Is there an easier way I can change all my connections to point to the test sql server?

I am going to relate this to my Oracle experience. I have Personal Oracle installed on my PC [your equivalent would be MSDE]. When I create a connection in my DBC, I use the same connection name as I am going to use when connecting to the production server. Once I put the app into production, the only thing that changed are the parameters in that connection of the same name.

In Oracle, we have a HOSTS file [tnsnames.ora] that contains host names [aliases]. Along with these names are all the connection parameters -- protocol [TCP/IP, etc], domain, address [e.g., IP Address of the host] and the port.

Since this is already set up for my users, I have to do nothing. My hosts file contains the parameters to connect to my Personal Oracle, and their's has the same host name I use but with parameters that point them to the production database.