Crystal Report Problem Please Help

Question

5.00/5 (3 votes)

See more: (untagged)

I'm using a stored procedure to populate a crystal report, But I get repeatative(duplicated) information on my report- something like 66 pages instead of atleast 2. I want to produce a transactions statement for a particular user, using the crystal report, with the stored procedure getting data from multiple tables, accepting as a parameter the name of a particular client(user). Am I using the crystal report for good purpose or may be the stored procedure isn't just a way of doing it?
[confused]

Posted 11-Aug-09 7:38am

Andile.M

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

David Mujica · Accepted Answer · 2009-08-11T08:02:00

You should be able to use a stored procedure as the datasource for a Crystal report.

1) Verify that when you execute the sproc outside of crystal it is returning the correct number of rows.
2) Make sure you are not performing some join in crystal which is giving you too many unexpected row.

My vision would be that the sproc would return all of the data necessary to generate the report and you would not have to join to any other table for reference data (like user first name, last name, etc), this would make designing the report very straight forward.

Hope this helps. [thumbs up]