>>re-read my earlier post...
>
>No, I won't read your earlier post again. It made no sense. I have clearly laid out the correct syntax and have posed the BIG QUESTION where SQL Server gets the answer correct which you have not addressed.
>
>End of the Discussion is that the following is the correct FoxPro (not SQL Server) syntax. Read the FoxPro Help. I have no idea what your code is all about other than it doesn't make any sense at all.
>
>update y set y.d1 = x.d2 from junk y inner join junk2 x on y.id = x.id &&works correctly
>
>Note: That it is "update y" not "update junk" and that's what the FoxPro Help says to do.


Jeff,

For me the problem is that you are not aliasing all your fields as you should always do, even in SQL Server; the fact that this time SQL gets the correct result does not mean that is good practice to let SQL identify the fields by its uniqueness, tomorrow you change one of the participating tables to include a d2 field and your code stops working, the syntax you used here is correct for both FoxPro and SQL and in my opinion the only one that is correct.