July 8, 2009 at 4:49 am
Hi guys, I am receiving the error:
The multi-part identifier could not be bound. Here is the code:
UPDATE dbo.tbl_fees
SET dbo.tbl_fees.TRCODE = DDTRNF.TRCODE,
dbo.tbl_fees.TRDATE = DDTRNF.TRDATE
From DDTRNF INNER JOIN dbo.tbl_fees
ON DLOAN = TLOAN
Not sure what the problem is.
Thank you
July 8, 2009 at 5:33 am
Hi,
If you can give DDL(for both tables),along with some data insertion script, it would be easier to solve that.
July 8, 2009 at 6:36 am
I'm wondering if both your tables might have the same column name DLOAN or TLOAN. If so, you need to fully qualify them -- TableName.ColumnName.
Eli
July 8, 2009 at 6:50 am
I'm wondering if both your tables might have the same column name DLOAN or TLOAN. If so, you need to fully qualify them -- TableName.ColumnName.
Eli
My Guess is that ambigous column name error will be given in that case.
July 8, 2009 at 6:50 am
I'm wondering if both your tables might have the same column name DLOAN or TLOAN. If so, you need to fully qualify them -- TableName.ColumnName.
Eli
My Guess is that ambigous column name error will be given in that case.
July 8, 2009 at 6:50 am
I'm wondering if both your tables might have the same column name DLOAN or TLOAN. If so, you need to fully qualify them -- TableName.ColumnName.
Eli
My Guess is that ambigous column name error will be given in that case.
July 8, 2009 at 8:33 am
trudye10 (7/8/2009)
Hi guys, I am receiving the error:The multi-part identifier could not be bound. Here is the code:
UPDATE dbo.tbl_fees
SET dbo.tbl_fees.TRCODE = DDTRNF.TRCODE,
dbo.tbl_fees.TRDATE = DDTRNF.TRDATE
From DDTRNF INNER JOIN dbo.tbl_fees
ON DLOAN = TLOAN
Not sure what the problem is.
Thank you
Greetings,
Please try changing your SET dbo.tbl_fees.TRCODE = DDTRNF.TRCODE, to SET TRCODE = DDTRNF.TRCODE, .
By putting the full qualification on the field name, your UPDATE statement might not be able to reference it back to the table it is already updating.
You could also change your INNER JOIN to WHERE DLOAN = TLOAN and it should still work.
Have a good day.
Terry Steadman
July 8, 2009 at 2:32 pm
Thank you all for your feed back. I solved it by changing the name of the fields on the output table.
Thank you so much for you quick and helpful responses.
Trudye
July 8, 2009 at 2:33 pm
Thank you all for your feed back. I solved it by changing the name of the fields on the output table.
Thank you so much for you quick and helpful responses.
Trudye
July 8, 2009 at 2:34 pm
Thank you all for your feed back. I solved it by changing the name of the fields on the output table.
Thank you so much for you quick and helpful responses.
Trudye
July 8, 2009 at 2:38 pm
Thank you all for your feed back. I solved it by changing the name of the fields on the output table.
Thank you so much for you quick and helpful responses.
Trudye
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply