ROWLOCK is being used.  Might there be a conflict if another is altering the record that the cursor is currently trying to update? 

Otherwise,...

No we aren't.  It is simply a hard and fast rule of his. 

While I agree that set based is best, it is not the only solution.  Hence, not allowing...

Don't misunderstand me.  I agree that "being difficult" is one of the jobs of a good DBA.  But this guy is beyond that.  He will make up rules without good...

Probably correct Remi - and it is always good to have a calendar table.  But I was just giving an alternative if the person wanted to simply pass in the word...

Another possible solution might be the following: 

DECLARE @Month varchar(10),

                @Year varchar(4),

                @Date char(2), 

                @FinalDate datetime,

                @LastDayOfMonth char(2)  

SET @Month = 'April'

SET @Year = '2005'...

Thanks buddy. 

Thank you for the explanation.  When this post first started, you wanted only one record for each ASPECT_ID or AGENT_NAME.  To that end, we can help you set this...

You should be able to merge the columns within the selection contstraint: i.e..

WHERE CONVERT( varchar, CONVERT( smalldatetime, [Month] + '/01/' + [Year]) BETWEEN '01/01/2005' AND '07/01/2005'

That should not...

One thing I do not get.  ParentID was included in the original query, but not in the solution(s).  Is this field necessary?  And if so, where is coming from, (i.e.,...

Sushila is the MASTER at understanding and interpretting!  I have been too busy to get back to this, but her remarks fit my designs exactly!  Thanks.  [you fit Ten Centuries]...

You initmated that you needed dates for a BETWEEN statement within your code.  Is that still necessary?  If so, could you show us the code and explain what you want? ...

I am 'assuming' you need a recordset returned.  [Again, the BullDozer (Bully?) raises its ugly head].  Here is a possible, though not necessarily elegant or efficient solution: 

DECLARE @BeginDate...

Thank you sushila!  That is better than how I would have answered.  Exactly correct!   

Salvatore, the ball is in your court now......

I know from my past with this, grids are often third party components and a real bear to alter.  I whole-heartedly agree with Remi, though.  If you can do this...

I have used ALTER TABLE to insert columns into a #TempTable using Dynamic SQL in the past.  That may be a possible approach to ease the pain.  I agree with Remi...