Is there any way to use the SQL case statement logic to create a column in Access? I am using Access 2000 & the following is the statemnt I am trying to add as a column.
CASE WHEN (T1."ProductClass" IN...
Here is a thought...
Since you are using a stored proc, have the proc return result set be for col1, col2, col3, etc. The value of col1, col2, col3, etc. can be returned from the parameter(s).
The Crystal report would then contain col1, col2, col3, etc. which would probably have to be generic...
Chuck,
Do your Crystal reports contain the database name when saved? Check by going to Database & seeing if the server name is displayed.
You may want to try creating the reports against an alias database name. If you have a seperate web server per environment, you will not need to change...
I have run into this in the past.
A work around to try is to make a copy of the stored proc, set location to the copy, save, then set location back to the old proc & save. You can then delete the copy of the proc that you no longer need. This usually works for me.
I ran into a similiar problem some time back. Reports we had were displaying goofy numbers, but only in Excel. In our case, it turns out that Excel was recalculating the group footer & report totals & including data that was in the report header. For example, our report header had a cost...
Crystal will only display the first result set it receives from the stored proc. You will need to return a single result set that contains all the data you need. Rename the fields as needed,
e.g.,
instead of
select * from tmp_HdrPurchase
select * from tmp_DetPurchase
select * from...
If you change the name of the stored proc, you will have to do a set location to point the report to the renamed proc.
Why is the stored proc name changing?
Do you count tickets that were open for several weeks but are now closed or just open tickets when the report is generated?
If I understand you correctly, any ticket that is open today has to be counted for every week since it opened. Therefore, you count the number of open tickets, grouped...
We do not make any changes when going from dev to integ or from integ to prod. We just move the server that the sql.ini is pointed to for Sybase or the alias set up in our client network utility for SQL Server.
Have you tried creating an alias for your dev box database? When you are ready to move to production, go into your client network utility for SQL Server & edit the alias so that it points to the production box instead of dev.
No changes will need to be made to the report.
I always create an alias for my database connection & use that alias for connecting my report to the database. This way, when I switch from dev to test to production, I am switching the sql.ini file on my machine & not touching the report.
Has anyone used Crystal Reports against IXOS? We are going to start using IXOS as our archiving tool & I have been asked about using CR against IXOS. In particular, any helpful hints, specific problem areas,etc. would be appreciated.
KCM
In your procedure, you will need to add a group by statement.
Group By customernumber
Keep in mind that the other fields in your proc's select statement will either need to be include in the group by or have some kind of compute (MAX, MIN, SUM, AVG) performed within your select statement...
You can try inserting an additional report footer, placing the next crosstab in a report footer(report footer b) and placing the table header in report footer a. Format section report footer b and select new page after. Repeat with as many report footers as you need.
I'm not familiar with...
Frank,
I use stored procs (with many temp tables) alot & have found the best approach is to test by running the proc in SQL, like with SQL Programmer. If your proc comes back with more than one result set, Crystal gets very cranky. Even print statements can throw your report off.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.