Solved

Error 3075. DAO.Database Syntax error(missing operator) in SQL statement

Posted on 2010-09-24
8
992 Views
Last Modified: 2012-05-10
When executing the attached SQL statement in a function I get "Error 3075 in query expression 'PUB_INvcHead.CustNum=tblCust.CustNum INNER JOIN PUB_ShipTo ON (PUB_InvcDtl.CustNum = PUB_Shipto.CustNum' ". I created the statement by copying a workable SQL statement. I added the PUB_ShipTo to it. What is missing? I cannot see anything amiss.
Please let me know if there is a better clearer method of attaching the code.
Thanks
strSQL = "SELECT tblCust.CustID, tblCust.Name, tblCust.SupplierNumber, " & _
    "PUB_InvcHead.CustNum, PUB_InvcHead.InvoiceDate, Format([InvoiceDate]," & Chr(34) & invdat & Chr(34) & ") AS InvDatEDI, " & _
    "PUB_InvcHead.InvoiceType, PUB_InvcHead.InvoiceNum, PUB_InvcHead.InvoiceAmt, PUB_InvcDtl.InvoiceLine, " & _
    "qrsOrderHedDtlInv.OrderNum, qrsOrderHedDtlInv.PONum, qrsOrderHedDtlInv.BYName, qrsOrderHedDtlInv.BYPlantCode, " & _
    "IIf([ItemNum] Is Not Null And [ItemNum]<>" & Chr(34) & Chr(34) & ",[ItemNum],1) AS ItNum, " & _
    "PUB_InvcDtl.PartNum, PUB_InvcDtl.ShipDate, PUB_InvcDtl.PackNum, PUB_InvcDtl.OurShipQty, " & _
    "PUB_InvcDtl.UnitPrice, NZ([XPartNum]," & Chr(34) & Chr(34) & ") AS CustPNum, PUB_InvcDtl.ExtPrice, " & _
    "PUB_InvcDtl.PackLine, tblCust.EDICode, PUB_ShipTo.Name As STName, PUB_ShipTo.Address1, PUB_ShipTo.Address2, " & _
    "PUB_ShipTo.City, PUB_ShipTo.State, PUB_ShipTo.Zip, PUB_ShipTo.Country " & _
    "FROM ((PUB_InvcHead INNER JOIN PUB_InvcDtl ON PUB_InvcHead.InvoiceNum = PUB_InvcDtl.InvoiceNum) " & _
    "LEFT JOIN qrsOrderHedDtlInv ON (PUB_InvcDtl.OrderNum = qrsOrderHedDtlInv.OrderNum) AND " & _
    "(PUB_InvcDtl.OrderLine = qrsOrderHedDtlInv.OrderLine)) " & _
    "INNER JOIN tblCust ON (PUB_InvcHead.CustNum = tblCust.CustNum) " & _
    "INNER JOIN PUB_ShipTo ON (PUB_InvcDtl.CustNum = PUB_ShipTo.CustNum) AND (PUB_InvcDtl.ShipToNum = PUB_ShipTo.ShipToNum) " & _
    "WHERE (((PUB_InvcHead.CustNum) =" & [Forms]![frmInvEntry]![cmbCustNum] & ") And " & _
    "((PUB_InvcHead.InvoiceDate) =#" & [Forms]![frmInvEntry]![txtInvDate] & "#) And " & _
    "((PUB_InvcHead.InvoiceType) = " & Chr(34) & SType & Chr(34) & ") And " & _
    "((tblCust.EDICode) Is Not Null And (tblCust.EDICode) <> " & Chr(34) & Chr(34) & ")) " & _
    "ORDER BY PUB_InvcHead.InvoiceNum, PUB_InvcDtl.InvoiceLine;"

Open in new window

0
Comment
Question by:StampIT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
8 Comments
 
LVL 57
ID: 33755729
<<Please let me know if there is a better clearer method of attaching the code.>>
  Nope, that's it.
<< What is missing? >>

 Probably a ).   I would try and break it down.  First, chop off the WHERE and ORDER BY clauses and try executing.  If an error, then eliminate all the SELECT's fields except for one field.  If it still fails (and this is probably where it is), then it's the joins.
User the query designer to get the join syntax you need.  You can design it graphically and then switch to SQL view, or play in SQL view and build the statement up slowly switching to design view as you progress.  If you get an error, then you know what you just did is at fault.
JimD.
0
 
LVL 57
ID: 33755748
BTW,  you've got a couple of these in there:
& Chr(34) & Chr(34)
 Which doesn't look quite right.  Either you meant to stick a value in there and didn't, or you included an extra quote (chr$(34)) by mistake.
JimD.
0
 
LVL 2

Expert Comment

by:godspropy
ID: 33755845
I'm no MS Access expert but I have never seen # characters used that way in SQL.

I would try replacing:

#" & [Forms]![frmInvEntry]![txtInvDate] & "#

with:

" & [Forms]![frmInvEntry]![txtInvDate] & "
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 57
ID: 33756039
godspropy,
#'s are delimiters to indicate date/time fields in JET SQL
JimD
0
 

Author Comment

by:StampIT
ID: 33771265
JimD,
   Thanks for the comments. To create the SQL statement that generates the error I copied from the attached code. The attached runs fine. I added some fields and the last INNER JOIN for the PUB_ShipTo table. So doing as you suggest, eliminating the last INNER JOIN I know the statement will work. Also I did create the query graphically first. The way I have the last INNER JOIN is the way it is when I switch the graphical query to SQL. Is there anything else I can try?
strSQL = "SELECT tblCust.CustID, tblCust.Name, tblCust.SupplierNumber, " & _
    "PUB_InvcHead.CustNum, PUB_InvcHead.InvoiceDate, Format([InvoiceDate]," & Chr(34) & invdat & Chr(34) & ") AS InvDatEDI, " & _
    "PUB_InvcHead.InvoiceType, PUB_InvcHead.InvoiceNum, PUB_InvcHead.InvoiceAmt, PUB_InvcDtl.InvoiceLine, " & _
    "qrsOrderHedDtlInv.OrderNum, qrsOrderHedDtlInv.PONum, " & _
    "IIf([ItemNum] Is Not Null And [ItemNum]<>" & Chr(34) & Chr(34) & ",[ItemNum],1) AS ItNum, " & _
    "PUB_InvcDtl.PartNum, PUB_InvcDtl.ShipDate, PUB_InvcDtl.PackNum, PUB_InvcDtl.OurShipQty, " & _
    "PUB_InvcDtl.UnitPrice, NZ([XPartNum]," & Chr(34) & Chr(34) & ") AS CustPNum, PUB_InvcDtl.ExtPrice, PUB_InvcDtl.PackLine, tblCust.EDICode " & _
    "FROM ((PUB_InvcHead INNER JOIN PUB_InvcDtl ON PUB_InvcHead.InvoiceNum = PUB_InvcDtl.InvoiceNum) " & _
    "LEFT JOIN qrsOrderHedDtlInv ON (PUB_InvcDtl.OrderNum = qrsOrderHedDtlInv.OrderNum) AND " & _
    "(PUB_InvcDtl.OrderLine = qrsOrderHedDtlInv.OrderLine)) INNER JOIN tblCust ON PUB_InvcHead.CustNum = tblCust.CustNum " & _
    "WHERE (((PUB_InvcHead.CustNum) =" & [Forms]![frmInvEntry]![cmbCustNum] & ") And " & _
    "((PUB_InvcHead.InvoiceDate) =#" & [Forms]![frmInvEntry]![txtInvDate] & "#) And " & _
    "((PUB_InvcHead.InvoiceType) = " & Chr(34) & SType & Chr(34) & ") And " & _
    "((tblCust.EDICode) Is Not Null And (tblCust.EDICode) <> " & Chr(34) & Chr(34) & ")) " & _
    "ORDER BY PUB_InvcHead.InvoiceNum, PUB_InvcDtl.InvoiceLine;"

Open in new window

0
 
LVL 57

Accepted Solution

by:
Jim Dettman (Microsoft MVP/ EE MVE) earned 500 total points
ID: 33772721
<<Also I did create the query graphically first. The way I have the last INNER JOIN is the way it is when I switch the graphical query to SQL. Is there anything else I can try? >>
And if you take the statement that is giving you an error and past it into SQL view and attempt to switch to graphical view it does not give you an error and runs fine?
I don't understand why your getting a syntax error then...
JimD.
0
 

Author Closing Comment

by:StampIT
ID: 33773258
JimD,
   Not sure what was missing initially but I did as you suggested and pasted the SQL statement into  SQL view. I received the same error. So I copied only the FROM to before the WHERE part of the statement that worked in the SQL view and pasted this into the SQL statement in the code and it worked. Thanks.
0
 
LVL 57
ID: 33773364
Probably a )  and that's why I came back and I asked again; those are HARD to spot.
I often go back and forth with the designer until I figure out where the problem is.
JimD.
0

Featured Post

Simplifying Server Workload Migrations

This use case outlines the migration challenges that organizations face and how the Acronis AnyData Engine supports physical-to-physical (P2P), physical-to-virtual (P2V), virtual to physical (V2P), and cross-virtual (V2V) migration scenarios to address these challenges.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Phishing attempts can come in all forms, shapes and sizes. No matter how familiar you think you are with them, always remember to take extra precaution when opening an email with attachments or links.
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Familiarize people with the process of utilizing SQL Server views from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Microsoft Access…
In Microsoft Access, learn different ways of passing a string value within a string argument. Also learn what a “Type Mis-match” error is about.

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question