Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 313
  • Last Modified:

NEED TO BUILT A REPORT LIKE THIS

I HAVE ATTACHED TWO FILES ONE IS REPORT FORMAT AND ONE IS STORED PROC.

NEED HELP TO PASS MULTIPLE DIVSION NAMES IN THE @DIVISIONNAME PARAMETER

LIKE @DIVISIONNAME= 'dIVISION DESCRIPTION 2,DIVISION DESCRIPTION 3'

NOW IT ACCEPTS ONLY ONE LIKE THIS

@DIVISIONNAME= 'dIVISION DESCRIPTION 2'

ITS URGENT PLEASE
rpteBidProjectDetailCosting.pdf
StoredProc.txt
0
sqlcurious
Asked:
sqlcurious
  • 2
1 Solution
 
ValentinoVBI ConsultantCommented:
I think you'll find the answer in the following article: http://www.experts-exchange.com/Microsoft/Development/MS-SQL-Server/MS-SQL_Reporting/A_2002-Reporting-On-Data-From-Stored-Procedures-part-2.html

It explains in detail how you can pass a multi-valued parameter to a stored procedure, exactly what you're looking for :-)
0
 
sqlcuriousAuthor Commented:
please check the stored proc too is it possible from this stored proc if not can you modify
0
 
ValentinoVBI ConsultantCommented:
The following code assumes that the function called list_to_tbl as shown in the code snippet below exists.
(Please note: this function differs slightly from the one in the article because you're dealing with strings instead of numbers)

To filter on your divisions, instead of

 set @SQL= @Sql + ' And D.DivisionName LIKE ''%'+@DivisionName+'%''' 

Open in new window


you can do

set @SQL= @Sql + ' And D.DivisionName IN (select * from list_to_tbl(@DivisionName))' 

Open in new window


Please note that the declaration of your @DivisionName parameter should take into account that multiple values are passed.  Which means that the length of the parameter should be: maximum length of division name multiplied by maximum number of divisions that the report user will select.

One more note: I notice that you've also got DivisionIDs in your database.  It would be better if you could set up your parameter to use that ID as value for the parameter.  That way you get a list of comma-separated numbers (as explained in the article referenced earlier) instead of strings.  Obviously that means that your stored proc code would also need to change a bit.
That's just a note though, your method will work too.

Hope this helps?

CREATE FUNCTION list_to_tbl (@list nvarchar(MAX)) 
   RETURNS @tbl TABLE (string varchar(250) NOT NULL) AS 
BEGIN 
   DECLARE @pos        int, 
           @nextpos    int, 
           @valuelen   int 

   SELECT @pos = 0, @nextpos = 1 

   WHILE @nextpos > 0 
   BEGIN 
      SELECT @nextpos = charindex(',', @list, @pos + 1) 
      SELECT @valuelen = CASE WHEN @nextpos > 0 
                              THEN @nextpos 
                              ELSE len(@list) + 1 
                         END - @pos - 1 
      INSERT @tbl (string) 
         VALUES (substring(@list, @pos + 1, @valuelen))
      SELECT @pos = @nextpos 
   END 
  RETURN 
END

Open in new window

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now