I have a report (Crystal XI) that returns data about support tickets - basic info, like who opened it, closed it, etc...  Each record is another ticket, i.e. the ticket data is in the details section.
I need to add the amount of time that each ticket has been worked.  Unfortunately, that is determined by a stored procedure that takes the ticket id as a parameter.  I can't find a way to embed the stored procedure in the details section and have it automatically use a given field as it's input.
I had considered replicating the logic in the sproc in CR, but this stored procedure is absolutely hideous.  It also doesn't help that this database (SQL Server 2005, running in SQL 2000 compatibility mode) is the backend for an off the shelf ticketing application that we can't mess with too much - at least not directly.
Is anyone familiar with how to do this, or am I far too incoherent to help?

I had tried that in the past, and here's what ends up happening.

I add the sproc via the database expert, and a popup requests the parameter to be sent to the sproc, with the checkbox automatically checked for 'Set to Null'.  I set the join up correctly between the two, and refreshing the report returns no data as the parameter is set to null.  I don't want to explicitly state what the value of that parameter should be, but it seems that I either need to pick a value or set it to null in order for the report to run.

When you add a stored proc to a report, it asks for the parameter so that it can determine the fields that the stored proc returns.  It is not the ONLY value that stored proc is going to use.  When you link the stored proc and the table, it would be like linking 2 tables.