error 3061

I have a simple update query, run from a form but does not contain form references, just table.fields.  This runs fine in my test environment but fails when I run it in the production environment.  I don't know of any difference in the two environments that would be related to this error (obviously, I'm missing something).   A very similar query runs fine just before this one.  I've tried removing the Where clause but the error  (3061, Too few Parameters, Expected 1) still occurs.  
Any suggestions will be greatly appreciated.
Thanks,
Brent
'Update table from imported data
   strSQL = "UPDATE [RouteCards_temp]" & _
         " INNER JOIN StreetSyncOutput ON [RouteCards_temp].iCustId  = StreetSyncOutput.CustomerNumber" & _
         " SET [RouteCards_temp].Sequence = StreetSyncOutput.Sequence," & _
         " [RouteCards_temp].StopSequence = StreetSyncOutput.StopSequence" & _
         " [RouteCards_temp].RouteName = StreetSyncOutput.RouteName" & _
       " WHERE  RouteCards_temp.icustid > 0 ;"
         
   db.Execute strSQL, dbFailOnError

Open in new window

synergyconsultingConsultantAsked:
Who is Participating?
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.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Well, since there are no Form references and not WHERE issue, almost leaves a Typo

But, other things to try:

Check for any Missing References - in the VBA editor on the suspect machine.

Might as well do a Compact & Repair.

Almost seems like some minor differences between machines.

Can you eliminate more of the SQL to narrow it down ?

mx
0

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
mbizupCommented:
Since this is a difference between your Test and Production environments, have you ensured that any fields you may have added to the tables in your Test environment have also been added to the tables in your Production environment?

Missing fields are another cause of this error.
0
mbizupCommented:
Same for table names.  Just ensure that the database table structure is identical in both environments in addition to the actual code or SQL.
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

synergyconsultingConsultantAuthor Commented:
I've requested that this question be deleted for the following reason:

I found my solution.  Production database had a typo in a related field.
0
mbizupCommented:
<Production database had a typo in a related field.>

The comments here addressed that.
0
synergyconsultingConsultantAuthor Commented:
typo in field name in prod database.
0
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
"Well, since there are no Form references and not WHERE issue, almost leaves a Typo"
0
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.