SQL Server 2000, Crystal Reports 9

[hsandwick]

Creating views in DEV, then PROD - it is necessary to update all links in the Crystal Report to the different environment, correct? In other words, it is not possible to just copy over the report that's been created in DEV, to the PROD environment - all formulae, fields, subreports, etc., must be updated to point to the PROD view.

Thanks,

Helen

 

[Durango122]

hi
you need to set the databse location connection to the production database on all report.
you need to create odbc system dsn for the production and point the reports to the new dsn



Durango122
Remember to used all fingers when waving to policemen

 

[hsandwick]

Thanks, Durango122,

So, I'll always be testing against the PROD DB, unless I update the links to the DEV DB for testing purposes. I see.

Helen

 

[synapsevampire]

If you are using ODBC (don't if you use Oracle), you can change the ODBC driver to point to prod and you may not need to do anything else.

If you are using a diffferent connectivity, then use the Database->Set Datasource Location in each report and point ot the other source, it should update all objects for you.

There are tools that can assist you with this if you have numerous, such as Report Inspector.

-k

 

[hsandwick]

Yes, synapsvampire (and Durango122), I thought that was how it should be. Our current setup is confusing - our paths have been created identically for both DEV and PROD, so in ODBC and Crystal there's no way to differentiate - a little precarious. Although I was advised I'd be pointing to PROD in one scenario, and DEV in another, I tested it out, naming a view differently in PROD, and found that not to be the case. Your feedback will be helpful in making some suggestions.

So, once the environments have been correctly separated, as long as the names of the VIEWS in both DEV and PROD are the same, we should be fine. Sounds good.

Thanks,

Helen