Field Explorer is empty after establishing a connection to a SQL 2008 SP

Question

I am trying to create a report using a SQL Server 2008 stored procedure as the source of data using an ADO connection.
The stored procedure is slightly odd, in that its building up the SQL as a string, Below is a snippet of the code to show what I mean. The reason for this is that I need to build up the WHERE clause dependign on user input.
     SELECT @var_query = 'SELECT  c_source,
        c_ccy,
        n_quantity,
       a_price,
       d_price,
       a_isd
                     FROM     ldsdbo.lds_testing_filter_data_vw WHERE'
     PRINT @var_query
     EXEC (@var_query)
This runs fine in SQL Server, but when I try and use it in Crystal, the Database Field list is empty.
Does anyone know whats going on, and how I can make this work?
Thanks
Nathan

Answer 1

Well... Now I just feel obligated to reply...
The key(s) to using an SP as your data source is to make sure that your SP does in fact return a single data set.
So... begin by testing it in SSMS. If the following works in SSMS, then it should also work in CR...
EXEC usp_MyStoredProcedure 'ParamValue1', 'PramValue2'
... note: the above example is based on the premise that the SP name is "usp_MyStoredProcedure" and you are tryig two pass 'ParamValue1' & 'PramValue2' as values...
Obviously, you should use the actual SP name and any necessary test values if it has parameters.
Assuming that the SP executes in SSMS AND returns a result set, you should be good to go in CR... Just do as Don mentioned and make sure you are using the NC10 drivers.
If you are still getting stuck, remove the SP from the Database Expert and call the SP from a Command instead. It's easy to do as it allows you to use the exact syntax you used in SSMS. You'll just want to replace any hard coded values with CR parameters... (Just add the parameters to the parameter list of the command and reference them like this...
EXEC usp_MyStoredProcedure '{?Parameter1}', '{?Parameter2}'
HTH,
Jason