Awesome. Made a few tweaks and it worked like a charm. Thanks Jason!

Hi Adrian

Thanks for the suggestion!  Seems to work like a charm.  I found that it worked fine just by changing Start Position (1 Based) to zero.  Left the "Limit number...

Okay now it's starting to make sense!

A bit of clarification on my part first.  My code was not throwing the error when the sp_executesql call ran.  This ran, but accidentally...

Thanks for the response Philip.  Only thing I can think of is that right after my call to sp_executesql, I have this line:

select @error = @@error

I do this to capture...

Here's a little more detail.  I do have code in place at the top of my while loop that checks the sysobjects table to make sure the object exists before...

Okay folks here's an example that's been causing me some problems.  SQL Server 2000 environment:  I have a piece of code that executes some dynamic SQL which deletes database objects...

Thanks for responding, even though the issue is now moot.  Interesting approach RCAVILL, I'll keep that in mind in the future! 

Nevermind...

Since I am retrieving the data from a view I just coded around the issue by adding a column to the view containing a derived value that I can use...

Hi Bill

Thanks for the replies.  Sorry if I am confusing the issue.  What it comes down to is this:  If the stored proc fails due to a hard database error...

Thanks Bill.  That will indeed work from a functional perspective.  The only problem with it is that from DTS' perspective, the task will complete "successfully" even if the stored proc...

^^^ Interesting.  I've read several articles that stated that using functions around search arguments prevents the optimizer from using indexes.  (Including an article or two referenced on this site!)  Apparently...

I would go with your third option above.  The first option will needlessly scan through your address table looking for rows where STATE = null when all you really want...

No problem!  Glad it worked.  The IF statement still has plenty of utility.  I think of it primarily as a "control-of-flow" operator.  I use it in stored procedures a lot, to...

The problem is that you can't use an IF statement within the select as you have it structured.  Try the following, using a CASE statement instead:

Select

 case

 when ExEeTermDate > DATEADD(m, DATEDIFF(m,...

Yes, the clustered index will ensure that the rows are physically ordered based on the columns you specify in the index.  Some things to bear in mind:  You can only...