Trent

We were able to switch the database name up until we went to version 1.7x. That's when we noticed.



As you may recall, it's a group of us that team up to work on multiply projects. One of the biggest reasons why it was so important to have the ability to point the Strataframe Db to a different name is because of the multiply developers that may or may not have access to a particular DT project. We only want people to have access to what that should have, not see every DT project.



Purnell

Wow...I haven't looked up your account. But this hasn't been possible for at least 2 1/2 to 3 years....maybe longer. Greg already mentioned the reasons why.



As Greg already mentioned, you can delete the connections.dat and appkeys.dat to go in and reconfigure the connections. However, if you want to connect to the Lw_* database that is StrataFrame, then you will have to rename that database to StrataFrame.



One other potentially major issue that I see here is that if you renamed the StrataFrame database and have been updating, then that database will not get updated as we do not allow the database name to be modified during the installation. I highly recommend getting back to a standard naming convention for the StrataFrame database otherwise you will fight a number of other downstream issues.

This worked, but I still need Trent to give me a back door. In the future I may need to add new StrataFrame Data Stores that are NOT a database called StrataFrame on the same server. Purnell Glenn also needs this info when Trent posts.

Ross,



Trent will have to provide a backdoor for you, but I do remember when they changed this. They were having a ton of support issues because folks got confused about the difference between the SF database (containing the meta data used to build BO, security, etc.) and their other dbs.



As I think about it, you might try copying the Connections.dat and appkeys.dat from your original machine to the vista machine. That might get the job done, at least until you learn what the top secret hand shake is that allows you to change the name.

In VS2008, Select menu StrataFrame, then Database Connection. When I initially purchase SF about 18 months ago, when I installed SF, I set up SF Connection "StrataFrame Data Store" to point to a remote server with SQL Server Authentication and at that time I set the Database to LW_Main. This is a shared area that I user with multiple other programs (we each have our own licenses. We are working on a related project for a common client.

As a developer for other client's and do things in SF, that are totally unrelated to thabove common client, I created another SF Connection by adding a new one. This one was configured to connect to my localhost using Windows Integrated Security and just used the default database "StrataFrame".

Then I purchased a 2nd license for a VISTA machine, went through the SF Install, and then went to the StraFrame menu in VS2008, selected SQL Server Authentication, put in the correct user/password and the server address as I initially did above on my first license. Then issue now is that the Database dropdown no longer allows you to change the name of the database from "StrataFrame" to something else that I need such as the one that has already been set up called "LW_Main" and is shared by several developers.

I am thinking that at some point you could change this in an earlier release, and that MicfroFour eliminated this in some release after that. I need you to confirm this ASAP. If the database cannot be changed in the StrataFrame/Database Settings, is there a back door where I can change this? Or will we need to change the name of the database from "LW_Main" to "StrataFrame"?