Just to recap.  Below is a script that will produce the environment.  Once you have the environment created, write a sql statement that will do the same as the following statement...

I don't want to eliminate the nulls.  That is the point the *= syntax does not eliminate the nulls which is the desired result.  I am not trying to change...

Nice try, 

I went that route as well.  I tried

from table2 t2 left outer join table1 t1 on t1.id=t2.id

from table2 t2 left outer join table1 t1 on t2.id=t1.id

from table1 t1 left outer join table2 t2 on t1.id=t2.id

from table1...

The statement with the *= join syntax is the correct and desired output.  Here is the english version of what I am trying to accomplish.  I have two tables that...

Thanks but I don't think that is correct either.  One, because I tried it and it produced yet another completly wrong recordset and two, because t2.data=2 and t1.data=5 should be...

Just a short additional note.

You dont have to reinstall to change from Windows Authentication to Windows and SQL Authentication.

You can access this property in either the registry[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\LoginMode] or through EM...

Sorry

I don't have any magic suggestions as to why this might be occurring.  The only thing that I would do at this point is try to get to the least...

Do you have the paramater @TruncateDeweyDecimalPlaces specified more than one place in your code?

I am assuming that you might be doing something like this.

string sql =...

Can you post the code .net snippit that you are using?

Thanks for the clarification Ray. 

Glad someone with a lot of expierence is watching over our sholder.

That is never a bad thing. 

Boy, the ideas just keep comming.

You could possibly seralize the data into xml (ie Select ... for xml) and pass the data like that.  Of course if your data exceeded...

I love for somone to tell me that something cannot be done.  It stimulates the thinking. 

It occurs to me that table is a type of variable such that

declare @t...

I have found that to be an inaccurate statement.  If the port is the standard SQL default, then it is accurate to say that the port is not required.  Once...

I am not aware of a way to do exactly what you are asking, but I think that there may be a work around.

If your SP is a simple select...

What a bunch of whiners.  You know life is not fair and all too often the problems we face...