Original sugession you were not agree with was:

SELECT P.[ProgramName],

 ISNULL(SUM([CasesReceived]),0

If you do something without knowing what are you doing you'll get unexpected results.

If you do sum(value1)+sum(value2) you'll get what is expected.

But if you do sum(value1+value2) you actually do not aggregate...

Which query are you trying to execute?

What is the error message?

What kind of data and which way you supply to that query?

If you don't know structure of your text you cannot build a script to modify it.

If you know enough to modify the text than you can dismantle it into pieces,...

Which way are you trying to insert UCS-2 into nvarchar?

Can you provide any sample of your script?

Probably you could do it with UPDATETEXT and PATINDEX.

But, honestly, it's easier to do it with simple macro in MS Word.

BLOB fields (and TEXT as a case of DLOB) are not a part of Relational Data model, so it not to be managed or processed by RDMS (and SQL Server as...

Yes, Sergiy here is still the same for at least 3 years.

Actually I don't look on my number of posts, only on others.

So...

No, that table must be imported from some hierarchical database.

So, you cannot find any key in table itself, you must know how and where this particular system holds the order...

Try something like this:

IF EXISTS (SELECT * FROM sysobjects WHERE  name = N'Find_Newest')

 DROP FUNCTION Find_Newest

GO

CREATE FUNCTION dbo.Find_Newest

 (@OldOne nvarchar(20) )

RETURNS nvarchar(20)

AS

BEGIN

Declare @N nvarchar(20), @O nvarchar(20)

Declare @Time datetime

select...

Tried to reproduce the error described in that article - no luck.

Everytime it inserts lines in right order.

Your way is quite dangerous. Rows may be not in order already.

Set up order right on data arrival:

SELECT Identity(int, 1,1) as ID, *

INTO test_table

FROM OPENQUERY(...) -- or whatever...

I'm afraid VB won't help.

Your rows will be shuffled after 1st update. And you could never restore the original order.

You definetely wrong about old system. It DOES hold the order...

So, you have nothing to do with this.

Sorry.

You must have lost some data when copied data from legacy system. Something you did not noticed made those rows consequtive. And now...

OK.

There are too many words. Lets keep it simple.

Write a SELECT to retrieve your "Row 2".

Can you do it?