The join syntax is different between Access and Sql server.

I don't know of any unpivot function in 2005.

However this works in any version :

--Insert into normalized table...

Select SerialNumber, AccountName, Op0Name AS OPName, Op0Date AS OPDate, Op0Value AS OPValue FROM...

Personally I would export all the sps text to a single text file.  Do my search and replaces there.  Run the alter scripts in QA environement.  Then once all typos...

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.