Rather than EXEC(@sql), could you PRINT @sql and show us the results? 

Thanks

What is the error that is generated? 

(Also, why are you doing this?) 

I am with RGR'us on this!  You will end up jumping through hoops not only to populate a single table, but retrieving the data will become a nightmare - not...

Nope - not a bit.  It was a poor assumption on my part that this application had an Access front end.   

If you...

Last query defnetely cannot return expected result.

It does return the expected results...

Agreed about the table scan and use of index or statistics - yours is a better query. ...

Try this: go to the query that is failing.  Look at it in Design View.  You will see in the upper left hand corner, (I am doing this from memory,...

I do not think that returns the requested results...

DECLARE @Table1 TABLE( id1 integer,

                                      data1 integer)

DECLARE @Table2 TABLE( id2 integer,

                                      data2 integer)

INSERT INTO @Table1...

Glad to help!    [I just updated the post by thinking about why the results returned as they did - I wrote a...

The more I think about this, the more it makes sense.  Microsoft states that old join style using *= will return "ambiguous" results.  This is a proof case! 

You have an additional...

I have tried two possible solutions, as I am not sure if you are always using lastname in your query... (I couldn't really test this, since our database is not...

I cut my teeth learning programming during a C class.  The teacher was incredible in showing fundamentals! He ended up being able to teach 3 semesters... it was the best! ...

LOL..., good one! 

"You keep thinkin' Sundance..., that's what you do best."   

yeah - I had this one laying around and answered too quickly...  

This will pump each value into a #TempTable.  You can alter this to pass each variable back after it is seperated or you could create your own #TempTable in your...