I have a similar issue.I started using a report was already

[ghevia99]

I started absed on one Crystal report was already created, and I reomved all the associated tables, and created the new ones, and I used I COMMAND, just to have a simple query.

Then, If I run the Report connected to DEV or  PROD, it works and very fast, around  1.6 secs.

I have created three Input Paremeters:

1. Plant #  ;  2 Initial_Date   ; 3. Final_Date.

Running the report locally on my PC, I used   Plant # = 02 ; Initial_Date = 04/01/2023 ; Final_Date = 04/30/2023  ( means 1 month ), where I know there are 25 records involved, and it takes  1.6 secs, but If I run from SAP BI, making the Schedule, and running right now, it takes more 40 minutes.  What I am missing here ?

I compared this report, and I noticed that as others reports, I have something in the TAB links in Database Expert, but in this one, I don't even have the TAB Links,  could be that the issue ?

If so, how can I fix it ?

[ghevia99]

Just to answer your questions  JWisseman ;

Questions:

1. What happens when you run the report directly in the Launchpad? (i.e. Not a schedule.)
   • If I click directly on the file Under SAP BI to execute it, I enter the parameters and it runs finem pretty much the sae time  I run locally, also I am able to export to excel very fast. when I execute by eschedule is when is taking long time to run.
2. What happens with a brand new report based on the same Command object SQL and parameters?
   • I have no other report using the same query, but If I run the query on SQL Developer it runs very fast as well.

[JWiseman]

Thanks for the info.

• Are there particular destinations or file formats that are causing the issue? e.g. If you schedule it to the default destination as a .rpt file does it work?
• Do a Save As in your enterprise environment as a new report and try to schedule that.
• If none of the above work create a new report just using that Command object, put all of the fields in the Details section, and schedule that.

Here's what I sometimes do if I've made changes to a report and it no longer works somewhere in the enterprise environment. Please do see Don's answer as well for further information.

1. Make a local backup copy of the report on your laptop...*** very important of course ***.
2. Go to to the enteprise environment and delete the report.
3. Save the local copy back into the enterprise environment.
4. See if it works.

[ghevia99]

And this is what I have in the report  when I click on Database Fields and  Database Expert, 

Then, inside  MFGDEV and all in Production is the same , I have this kind of Data Structure :

The Tables I need are in that list, but still I need to  re-added ?,

Then, should I replace the whole  folder  MFGDEV, and then do the same with all the others ?

[ghevia99]

Ok. I believe, It makes sense.

So, I am referencing 5 tables in my query, then I need to add each one of these table following the procedure :

1. In Crystal Reports, open the report.
2. Under the menu 'Database', select: 'Set Datasource Location'   
3. In the 'Current Data Source' section, click the data source to be changed.   
4. In the 'Replace with' section, click the data source you want the report to use.
5. Click 'Update'. 
6. Close the 'Set Datasource Location' window.
7. Save the report.

[DonWilliams]

The problem is the way you created the new report, it still has the old database connection info, which will work fine on your PC but when you send it off to someone else that connection will no longer work and that user has no connection to the previous DB.

CR keeps a copy of the DB info in the RPT file, even if it's not being used.

As Jamie indicated the reason the link option is available is because it has the old connection.

The delay is due to CR attempting to connect to the old data source....

Click on Database, Expert and remove the old connection, if it fails it's because there are still references to the original data source in the report somewhere, look at the report properties will show you where they are.

Create a new report, copy in the Command SQL and copy/paste int the various section info, fields etc.

Now it should work fine on the BI server...

[JWiseman]

Hi ghevia99, the Links tab will show up if there's more than 1 database object utilized on a report. If you are using a single Command object then there shouldn't be a Links tab.

Questions:

1. What happens when you run the report directly in the Launchpad? (i.e. Not a schedule.)
2. What happens with a brand new report based on the same Command object SQL and parameters?