Eddie, you forgot to mention that stored procedures may return no resultset.

It may be designed to work out data without any immediate output.

UPDATE Table1

SET Name = Table2.NewName

FROM Table2

WHERE Table2.OriginalName = Table1.Name

If my statement does not do it for you?

Book On Line.

"Help" for MSSQL 2000.

You can open it by pressing F1.

Did you read EXECUTE topic in BOL?

UPDATE tasks

  Set request = UpdateTo

  From NewList  

  Where request = MATCH

That's all.

No cursors.

Right approach.

You only need to change the order of statements:

UPDATE first, INSERT second

Otherwise you update just inserted rows.

CR is "Carriage Return", CHAR(13), 0D in HEX;

LF is "Line Feed", CHAR(10), 0A in HEX.

Standard text file in Windows uses both of them to start a new line.

Standard text...

If this is UNIX format file with only LF as line terminator or Win format with CR+LF?

CHAR(13), CHAR(10), CHAR(9)

But what they have become?

Your rows will become columns. Because your ROWTERMINATOR is 'DN:'

Why you did not import this file with field terminator = \n and rowterminator = 'DN:' ?

Compare resultset of EXEC proc_storedproc1  to column definitions for table1.

They must be different.

You better test before you say it.

Especially when you need to update 1 value in a row.

I also cannot imagine screen with 40 values on it. So, you don't select...