SQL Server/Crystal report issue

  • I'm somewhat new to Crystal and I'm writing reports based on stored procedures which is not the norm here so when I run into problems, I hear "I've never written a Crystal report from a stored procedure." I have 2 questions:

    1) Does anybody routinely do this?

    2) I wrote a rather complex stored procedure, created a report and it was working and published on Lawson's dashboard for testing. I changed something and changed the proc name (I don't remember why) and the report will not work now. And I have renamed the proc, created a new report based on the proc and it still won't work. Does anyone have any ideas on what could be the issue. The users that tested it want it bad and I am stuck. Any thoughts/suggestions would be greatly appreciated.

  • Have you tried verifying the database or checking the Database settings from within Crystal? Go to the Database menu to check all the settings and field mappings.

  • I've done that. It won't Verify and if I try to Change DataSource I just get in a loop. I feel like I need to reinstall Crystal or SQL Server, but not sure which. When I create a new stored proc in SQL Server, it's not giving me the permissions that it was giving me automatically. I'm stumped.

  • It could be a permissions issue on the procedure since you renamed it. Have you granted the appropriate user\group execute permissions? That's the only other thing I know to check.

  • Yes, I checked them and they were missing. Which is another odd thing. I've never had to add them myself.

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply