What you seem to need is a CROSSTAB/PIVOT like thisCREATE PROCEDURE dbo.VIEW_REPORTS

(

@BRC_START_DATE DATETIME,

@BRC_END_DATE DATETIME,

@Hild_Branch VARCHAR(50),

@REPORTSIZE INT,

@RPT_REPORT_NAME VARCHAR(10),

@USER_ID INT,

@ReportType_Code NVARCHAR(50)

)

AS

SET NOCOUNT ON

DECLARE @MonthFirstDate DATETIME

SET@MonthFirstDate = DATEADD(MONTH, DATEDIFF(MONTH, @BRC_END_DATE, '19000101'), '19000101')

SELECTb.BRC_BRANCH_CODE,

sum(case...

I also lack the oppurtunity to call the SP twice in a row.

I get an error "index already exists".

Change the anchor part to GROUP BY and add a COUNT for top level items.

Add a +1 in the recursive part.

Do you really want to SEAL the Internet? 🙂

I think you are getting a tree hierarchy.

Just use a WHILE loop instead.

Jeff, excellent code but I think you should start using QUOTENAME function for those having brackets, spaces or even single quotes in their table/column names.

I think OLE/AdoDB has a "refresh" method that will try to get the parameters with datatype and direction for you.

Are you trying to collapse datetime ranges?

http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=88422

Not for me.

I have tested on all these and your code gives exact same sum.

SQL Server Express 2005 9.0.3186

SQL Server Enterprise 2000 8.00.818

SQL Server Standard 2000 8.00.818

SQL Server Enterprise 2000...

As other has said before me, FLOAT is just an approximation based on binary storage of the number.

See here http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=81849

Can't you just change the datatype to DECIMAL(20, 12) ?

HOW is shown at this blog

http://weblogs.sqlteam.com/mladenp/archive/2007/10/01/SQL-Server-Notify-client-of-progress-in-a-long-running.aspx

Strange that when a problem is URGENT, the original poster always finds time to post the problem statement on several different sites...

SSC

http://www.sqlservercentral.com/articles/Advanced+Querying/howmanymoremondaysuntiliretire/2475/

Are instead-of-triggers available in SQL Server 2000?

I know "date Zero" is 1899-12-30 in both Access AND VB6. Not 1899-12-31.

So you are off by two days.