<div>
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. &nbsp;This will show you any syntax errors. &nbsp;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. &nbsp;Frequently you'll get a better error message.<br />
<br />
Put a stop on the line that executes the query. &nbsp;When the code stops, print SQL_PriFam_Qry to the window.
</div>


<div>
<div class="content wysiwyg-content">
The following code in Access 2016 gives me an &quot;expected end of statement error message&quot;.<br />
SQL_PriFam_Qry = &quot;UPDATE ClientInfo &quot;&nbsp;&amp; _<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &quot;SET ClientInfo.PrimaryClientNa<wbr />me_C = Nz(DLookUp(&quot;ClientID_FK&quot;,&quot;<wbr />Prospectiv<wbr />eClients&quot;,<wbr />&quot;ProspectI<wbr />D=&quot; &amp;&nbsp;[PrimaryClientName]),0), &quot;&nbsp;&amp; _<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &quot;&nbsp; &nbsp;ClientInfo.FamilyMember_C = Nz(DLookup(&quot;ClientID_FK&quot;, &quot;ProspectiveClients&quot;, &quot;ProspectID=&quot; &amp;&nbsp;[FamilyMember]), 0) &quot;&nbsp;&amp; _<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &quot;WHERE (((ClientInfo.ClientID)=14<wbr />94))&quot;
</div>
</div>


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))"

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&#39;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&#39;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.

Expected end of statement.

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

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Visual Basic for Applications (VBA) enables building user-defined functions (UDFs), automating processes and accessing Windows API and other low-level functionality through dynamic-link libraries (DLLs). VBA is closely related to Visual Basic and uses the Visual Basic Runtime Library, but it can normally only run code within a host application rather than as a standalone program. It can, however, be used to control one application from another via OLE Automation. VBA is built into most Microsoft Office applications.