To stored procedure or not to stored procedure 
Author Message
 To stored procedure or not to stored procedure

I'm working on an interface for our reports. The source of the reports
are recordsets. Currently, the sql statements are embeded in the
program. To run a report, our users select several criteria and show
the report based on the criteria built. I'm thinking of creating a sp
to return the recordset. One problem I would encounter with sp is that
the parameters have to be OR-ed.
For instance, my sp requires two parameters, state and id. If they want
to run by:
(state = CA and id = 12) or (state = TX and id 40).
How would would I make my parameters to be OR-ed.

Should I just create a COM-component?


Sent via http://www.*-*-*.com/
Share what you know. Learn what you don't.

Fri, 28 Dec 2001 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. To Stored Procedure or not to stored procedure

2. To stored procedure or not to stored procedure

3. sub report changes its source stored procedure to main report's stored procedure

4. ado recordsets from stored procedures, stored procedures have input parameters

5. More examples of using stored procedures / stored packages

6. Stored Procedure not working

7. Using Stored procedures or not?

8. Sql server stored procedures not returning a recordset...?

9. Recordsets not returned from stored procedures

10. Store procedure not Found in ASP?

11. Find method does not work on recordset obtained from stored procedure

12. Parameter to Stored Procedure CR 8.5 VB.Net Specified Cast Not Valid


Powered by phpBB® Forum Software