Query not working as designed

[SysDupe123]

I've been agonizing over this all day! This is the SQL for the query that I built:

UPDATE [Compl P129 A3C] INNER JOIN MasterFundSch ON [Compl P129 A3C].LOANNUMBER = MasterFundSch.[Loan Number] SET MasterFundSch.P129OldInv = [OLDINVNUMBER], MasterFundSch.P129OldCat = [OLDCATNUMBER], MasterFundSch.P129NewInv = [Compl P129 A3C]!NEWINVNUMBER, MasterFundSch.P129NewCat = [Compl P129 A3C]!NEWCATNUMBER, MasterFundSch.P129PrinBal = [PRINBAL], MasterFundSch.P129PrinTran = [Compl P129 A3C]!PRINTRANS, MasterFundSch.P129Diff = [PRINBAL]-[PRINTRANS], MasterFundSch.P129RptDt = [Compl P129 A3C]!RPTDATE, MasterFundSch.P129ActionCd = [Compl P129 A3C]!ACTIONCODE, MasterFundSch.P129DueDt = [Compl P129 A3C]!DUEDATE, MasterFundSch.P129EffDt = [Compl P129 A3C]!EFFDATE, MasterFundSch.[REPUR SUB] = IIf([groupID]="FH",IIf(Month([fund dt])=Month(Now()),IIf(Day([fund Dt])<16,"N","C"),"C"),Null)
WHERE (((MasterFundSch.P129RptDt) Is Null) AND (([Compl P129 A3C].NEWINVNUMBER)=[MasterFundSch]![New Inv]) AND (([Compl P129 A3C].NEWCATNUMBER)=[MasterFundSch]![New Cat]) AND (([Compl P129 A3C].ACTIONCODE)="0000" Or ([Compl P129 A3C].ACTIONCODE)="0820" Or ([Compl P129 A3C].ACTIONCODE)="0077" Or ([Compl P129 A3C].ACTIONCODE)="0078"));


I'm getting records updating that are not one of the four Action Codes that I've assigned.
Help before I go crazy!

 

[cmmrfrds]

I think it is easier to read if you get rid of some of the unnecessay parens. Normally the dot operator identifies fields.
WHERE
MasterFundSch.P129RptDt Is Null
AND [Compl P129 A3C].NEWINVNUMBER=[MasterFundSch].[New Inv]
AND [Compl P129 A3C].NEWCATNUMBER=[MasterFundSch].[New Cat]
AND ([Compl P129 A3C].ACTIONCODE IN ("0000" , "0820", "0077", "0078"))

 

[SysDupe123]

Yeah, it would be nicer to read, but Access seems to put them in. It still says the same thing. The problem is I get codes updating like "1040" and "DIF1" and they shouldn't!

 

[SysDupe123]

Got it. Over at UtterAccess, they suggested I use the
In() function instead of all the OR statements. Worked like a charm! Thanks anyway!

 

[lespaul]

That's what was suggested above?????

Leslie

Anything worth doing is a lot more difficult than it's worth - Unknown Induhvidual

Essential reading for anyone working with databases: The Fundamentals of Relational Database Design