The multi-part identifier could not be bound.

Question

1.00/5 (1 vote)

See more:

Hi... I want to update the details of Trns_Enrollmentmaster from Trns_Enrollmentdetails.. I'm passing few details from front end and remaining details updating from detail table...

When I'm trying to execute this query..I'm getting this error

The multi-part identifier could not be bound.

for those parameters taking from detail table...Can any one give suggestion for this.

What I have tried:

ALTER proc [dbo].[SP_T_PrimaryUpdate]


(@UHIDNO varchar(30),
@Yearautoid int,
@Membername varchar(50),
@ISPrimaryChanged bit,
@PrimaryChangeby varchar(50),
@Primarychangedon datetime,
@PrmaryChangedReason varchar(50),
@PrimaryChangedmembername varchar(50),
@PrimarychangeIP varchar(50))

AS
  BEGIN
        
        UPDATE Trns_Enrollmentmaster  SET Membername=@Membername,ISPrimaryChanged=@ISPrimaryChanged,
               Primarychangedon=@Primarychangedon,PrimaryChangeby=@PrimaryChangeby,PrimaryChangedmembername=@PrimaryChangedmembername,
               PrmaryChangedReason=@PrmaryChangedReason,
               PrimarychangeIP=@PrimarychangeIP, Age =a.age, Photo=a.photo, Gender = a.Gender
               
               SELECT a.age,a.photo,a.Gender FROM dbo.Trns_Enrollmentdetails AS a INNER JOIN dbo.Trns_Enrollmentmaster  ON a.UHIDNO=@UHIDNO and a.Yearautoid=@Yearautoid  AND Trns_Enrollmentmaster.UHIDNO=@UHIDNO AND Trns_Enrollmentmaster.Yearautoid=@Yearautoid 
      END

Posted 22-Feb-17 21:32pm

Developer29

Updated 18-Feb-20 0:50am

Add a Solution

Comments

Richard Deeming 23-Feb-17 16:25pm

When you get an error message, post the full error message. Don't paraphrase it; don't summarise it; don't simplify it. If you do, you risk removing the important information.

You should only ever remove sensitive information, like usernames, passwords, API keys, etc.

The full error message will look something like The multi-part identifier "..." could not be bound. The part within the quotes, which you have removed, tells you which identifier is causing the problem.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Graeme_Grant · Accepted Answer · 2017-02-22T22:26:00

Solution 1

Google is your friend. This search turned up a lot of possible answersa for you:
The multi-part identifier could not be bound. - Google Search[^]

... including this gem: sql - What is a 'multi-part identifier' and why can't it be bound? - Stack Overflow[^]

Posted 22-Feb-17 22:26pm

Graeme_Grant

Developer29 · Accepted Answer · 2017-05-12T18:59:00

Solution 2

There is a chance when using joins columns name may be same.. use alias name for the columns...It was worked in my case...

Posted 12-May-17 18:59pm

Developer29

Updated 17-May-17 20:38pm

v2

Comments

CHill60 18-May-17 5:10am

The situation you are describing would have resulted in the error "Ambiguous column name..." and NOT "The multi-part identifier ... could not be bound".
Your problem was the clause

PrimarychangeIP=@PrimarychangeIP, Age =a.age, Photo=a.photo, Gender = a.Gender

because you have used an alias a that is not defined anywhere in that UPDATE command.
If you want to do an update from a join then the (single) query should look like (untested)

UPDATE EM SET Membername=@Membername,ISPrimaryChanged=@ISPrimaryChanged,
       Primarychangedon=@Primarychangedon,PrimaryChangeby=@PrimaryChangeby,PrimaryChangedmembername=@PrimaryChangedmembername,
       PrmaryChangedReason=@PrmaryChangedReason,
       PrimarychangeIP=@PrimarychangeIP, Age =a.age, Photo=a.photo, Gender = a.Gender
FROM dbo.Trns_Enrollmentdetails AS a 
INNER JOIN dbo.Trns_Enrollmentmaster  AS EM ON a.UHIDNO=EM.UHIDNO AND a.Yearautoid=EM.Yearautoid
WHERE a.UHIDNO=@UHIDNO and a.Yearautoid=@Yearautoid

There is a clear example in my article Processing Loops in SQL Server[^] - look for "Updating Tables Using Joins"