Set Location for every report, do we have to?

[morechocolate]

We are going through a upgrade to a new system. The new system is on a different server then our current production environment.

We have several, hundereds in fact, so as you can imagine we really do not want to go through every report doing a Set Location. Is there a way to set up the ODBC configuration to avoid having to go into every report?

Thanks

 

[morechocolate]

I forgot to mention we are using 8.5

 

[Turkbear]

Hi,
By System, do you mean the datasource location ?

If so, you maybe able to edit the DSN used by the reports so that it 'points' to the new server ( assumes same data structure and table names)..
Not sure it will work, but may be worth a try..




To Paraphrase:"The Help you get is proportional to the Help you give.."

 

[morechocolate]

Thanks Turkbear - what I mean by system is our mortgage loan system is being update to a new version. We are putting the application on a new server, and once we go live the database name will be same name as it is on our current server. Also, for now, during the testing phase, we need the report to point to the testing database which on the new server as well.

I was trying to do what you suggested, but when it did not seem to be working I came here. I hopes were that someone would make a suggestion and help me realize what I may be doing incorrectly.

 

[synapsevampire]

There are also 3rd party products that do this, check out:

http://www.softwareforces.com/

-k

 

[morechocolate]

Thanks synapsevampire, but I am very confident that our company will allow me to go that route. They would much rather I go through 200+ reports doing Database | Set Location. From all the threads I have read it seems like for quite some time people have been frustrated by this reality. I would think BO would have come up with something themselves by now.