How does that fix the sort order?? aside from avoidig the problem?

I'm not sure I'm following here, what did you do exactly?

If there is I never hit it.  What problem are you encountering?

That works... but that's not without its share of downsides...

That's how close I can get it with the collation sort option.

DECLARE @demo TABLE (id INT NOT NULL IDENTITY(1,1), Name VARCHAR(50))

INSERT INTO @demo (Name) VALUES ('hello')

INSERT INTO @demo (Name) VALUES...

his name is Colin not Colon .

Declare @out as int

exec dbo.MyProc @out output

PRINT @out

You must supply the parameter in that fashion to execute the procedure.

I had similar problems once.  What I is create a new Access data project, and reconnect to the server and then selecting a db.  If that fails you can always reconnect...

Hence another advantage of using t-sql to make ddl changes :

alter table dbo.tblname

alter column a int not null

You can't change the columns' order that way, but you don't ever...

Check out books online.  It replaces all occurances of the @sArea in @Status3 with nothing ('').

Can you post the actual execution plan (text version pls)?  I'm sure something obvious is spliping by all.

I once saw someone use the clustered index in the indexhint.  I can't confirm this but it should guarante the order of the update.

Must have gone out of range of the datetime datatype... or a date setting has changed (but I'd go with the datetime limit).

And just to make sure we are on...

I don't think so.  I recently noticed that top 100 percent is automatically added to the view definition when using the order by, but it is not automatically removed when...

@@dbts is not a datetime.  It is only a unique number generated by sql server.

Check out GetDate() for the current_timestamp