Expected end of statement.

The following code in Access 2016 gives me an "expected end of statement error message".
SQL_PriFam_Qry = "UPDATE ClientInfo " & _
            "SET ClientInfo.PrimaryClientName_C = Nz(DLookUp("ClientID_FK","ProspectiveClients","ProspectID=" & [PrimaryClientName]),0), " & _
            "   ClientInfo.FamilyMember_C = Nz(DLookup("ClientID_FK", "ProspectiveClients", "ProspectID=" & [FamilyMember]), 0) " & _
            "WHERE (((ClientInfo.ClientID)=1494))"
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ryan ChongBusiness Systems Analyst , ex-Senior Application EngineerCommented:
you may try:

SQL_PriFam_Qry = "UPDATE ClientInfo " & _
            "SET ClientInfo.PrimaryClientName_C = Nz(DLookUp(""ClientID_FK"",""ProspectiveClients"",""ProspectID="" & [PrimaryClientName]),0), " & _
            "   ClientInfo.FamilyMember_C = Nz(DLookup(""ClientID_FK"", ""ProspectiveClients"", ""ProspectID="" & [FamilyMember]), 0) " & _
            "WHERE (((ClientInfo.ClientID)=1494))"

Open in new window


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
When you build SQL in VBA (which I rarely do since I prefer working with querydefs), you should always print it to the debug window to see what your actual string looks like.  This will show you any syntax errors.  If after you print the string, you still don't see the error, copy the string and paste it into the QBE in SQL View and see what Access has to say.  Frequently you'll get a better error message.

Put a stop on the line that executes the query.  When the code stops, print SQL_PriFam_Qry to the window.
VGuerra67Author Commented:
Thanks that works
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.