Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Use a non-excisting connection 1

Status
Not open for further replies.

acessn

Programmer
Feb 16, 2005
71
NO
Hi.

I'm using Crystal reports 9.0 with Kronos Workforce. Kronos comes with a lot of standard reports which freely can be moved between servers with different databases. This works fine, and the DataSource is "sql_smoke_440", which is a non-excisting DSN. I have no explanation to why the default reports is working everywhere, even if the database-names are different.


My problem occurs when I modify one of these reports, using a database on my local system and move them to a customer-server (which doesn't have CR installed) and run them from Kronos.
Then the report fails because of the datasource. Is there any way to select a datasource that doesn't excist on your local computer, but excist on the server you're moving the report to?

One solution is to install CR on the customer-server and change the datasource-location, but I only have remote access with limited speed, so this is not preferred.

All databases have the excact same structure just with different names.

Regards Bjørn Kaarstein
InTime Nordic as
Norway
 
I think this is related to schema names.

If you look at your Report SQL statement, Database - Show SQL Query, scroll down to the FROM section and in Your reports you will see Table Prefixed with Schema Name
"Schema Name"."Table Name"

In the Kronos Reports the Schema name has probably been removed.

To do this in CR9 go to Database Set Data Source Location, click on + next table and then again for Properties.

Double Click Overridden Qualified Table Name and then Type in the Full table name again. Click anywhere in White space and wait for Source to update, then Close.

Go to Crystal Knowledgebase and type "Overridden Qualified Table Name" into search and it will give you a more detailed explanation.

Return to Database - Show SQL Query and you will see Schema name removed. Do this to all tables and report should now be portable across all schemas provided table names are the same.

Hope this solves your problem

Ian Waterman
UK Crystal Reports Consultant
 
This fixed the problem. Thanks a lot!

Regards Bjørn
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top