It's not obvious where these prints come from:

W (4):

W (5):

W (6): 23517

...

Check your data.

Something makes the values not the same.

Double spaces, space in front, line feed at the end of the fields values, anything else what could make the difference.

And would be wrong.

Please run these 2 queries:

SELECT count(*) FROM < Table Name > WHERE SoldYr1 < 0 AND SoldYr2 = 0

and

SELECT CASE WHEN t.SoldYR1 > t.SoldYR2

...

aevans1981 (11/4/2008)

---

First, thanks for a great function, however...

I have read through most of this post, but not all, I am using the code that was originally supplied.

When I try fn_WorkDays(27/10/2008...

If you don't know what is UNC notation you may always google it.

1st, you don't need USE.

Just point on required database when call procredure :

EXEC DatabaseName.dbo.ProcedureName

2nd, as soon as you know the name of user who creates the table(s) just inside procedure...

Then use SELECT instead of PRINT.

But it's more resource consuming.

Wouldn't it be easier just to print the values you want to see during SP execution?

What generates those XML's?

IP address does not belong here.

Use proper UNC notation.

Replace "Z:\" with full network path:

"\\Server\Folder\Folder\...\log.txt"

Must help.

Try

ORDER BY [Committee Name]

for both options.

select @periodArray = ISNULL(@periodArray + ',', '') + Period

from @myTable

select @periodArray

Much less typing.

🙂

The way to go here is to retrieve whole XML string from the field, pass it to the application which suppose to parse XML and store parsing results in database...