All - thanks for your replies. Using the suggestions I was able to pinpoint the "non-compliant" stored procedure. To test the problem: I took the SQL Server2000 stored procedure and loaded that in SQL Server 2008 R2 native database mode and there was the error: Msg 209, Level 16, State 1, Procedure nspCartonization, Line 1154 Ambiguous column name OrderKey Msg 209, Level 16, State 1, Procedure nspCartonization, Line 1154 Ambiguous column name CartonGroup SQL SERVER 2008 NATIVE MODE - NO LONGER ALLOWED syntax: SELECT OrderKey, CartonGroup, * FROM TABLE ==>> This has duplicated column names and execution / compile of the procedure fails. Problem solved with: SELECT OrderKey, CartonGroup FROM TABLE or SELECT * FROM TABLE The application Runtime has no longer this error. Best Regards, Anton

I have seen that error when using a column name in the ORDER BY clause even where there is no other column possible. 

Work around is to order the relative column number of the columns.  for example ....ORDER BY 2 , 1 desc 

It is possible that the 2008 server has tighter rules than that of the 2000 server.

Try pre-pending the table name to the columns names and see if that helps.

Sometimes using an alias instead of the actual table name is easier to do.

 

Example:

SELECT  column1  FROM  table1;

becomes

SELECT  T1.column1 FROM  table 1  T1;

 

Olan

​