Skip to Content
author's profile photo Former Member
Former Member

Crystal freezes when changing stored procedure

Hi,

I have a problem modifying a report. The report runs from a stored procedure, with many parameters in the stored procedure. The sp itself doesn't use most of these parameters, but I need them to be in there, because the reports are run from a third-party application that can either use crystal parameters or stored procedure parameters, but not both, so most parameters are used from crystal.

The problem I have is that when I try to add a new parameter (of type nvarchar(27)) to the sp, the report stops working completely in crystal (it displays "accessing database", will sometimes get to "reading records 2/2", then freezes). Nothing else has changed in the report, and the sp still runs fine in about 4 seconds in SQL Server management studio.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Posted on Jul 30, 2008 at 07:21 PM

    Hi Charles,

    I will suggest to do a verify database to ensure Crystal Reports detected the changes you have made in your stored procedure.

    To verify database:

    - Select "Verify Database" under the menu "Database"

    Once this is done, your new parameter should then be added to the report, and you should be able to refresh the report.

    If you are still experiencing an issue, I will then suggest for testing purposes to verify if creating a new report of that stored procedure works.

    Patrick

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      I'd actually done the verify database, and since I suspected the problem would not crop up again if I just started off a new report off of this stored proc, and did not want to redo the report completely to check if the problem came back, I instead re-created the stored procedure with a different name, and used set datasource location to point to the new SP. I really don't understand why, but that solved the problem...

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.