I totally agree with Sergiy on this!  A default value is vastly different than the lack of information. 

Do it all the time.  Thanks!  (beautiful thing, that...)

(bit of a bang up today, (our car was hit on the way to work - not so good) so I...

Thanks.  I was thinking about that approach - of course I'm dealing with a large #TempTable throughout the procedure, but maybe I can pass the information back and fourth...

Are you joining the other #temp table to your pt61_table_load table?

OMG!  Thanks Eddie! 

We just started using 2005 and I completely misinterpretted the question.  We are only beginning to use these, so that information was extremely timely! 

Thanks [I should...

Why can't they be re-used?  If needs be, Truncate or Delete them, (I am not sure if Deleting a @TableVariable still fills the Trans Log - it may also cause...

You've already established the "Results" field in your new report table as varchar(8000).  Hence, you have to substring "Results" or make mutiple fields to hold the extra values... 

(Also, follow...

Hadn't even looked at that, but I agree Sql Junkie.  A cursor does not look to be necessary. 

What errors were you recieving when you split "Results" up?  Same thing? ...

The easiest solution is SUBSTRING( Results, 1, 8000).  But you may want everything contained within that field.  I don't know...

I'm not clear why you cannot use "Dynamic SQL" within a Stored Procedure passing the selected values by your client. 

If you can use this approach, please read the following...

Please do not cross post - you will get an answer

Microsoft specifically states that left and right outer Joins are not supported and in some cases “results in an ambiguous query that can be interpreted...

I added a customer table so you would have names displayed.  If I am understanding this correctly, hCrtlNum is not necessary to this query...

DECLARE @Payment TABLE( hCtrlNum numeric(18, 0)...

You probably should give more information.  An INNER JOIN will work, unless you want some aggregate or something along those lines in which a one to many situation exists:

SELECT...

Try it in your Development db.  These Triggers are there for a reason and you may find later the data integrity or even you front-end is goofed up by dropping...