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'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