Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1042
  • Last Modified:

Error 3079: The specified field 'Product Code' could refer to more than one table listen in the FROM clause of your SQL statement

I get this error only on the new workstations...

It has been working on 25+ computers for years.... it is not working with new computer, which has Access 2003.

Surprisingly enough, another PC, which was upgraded to MS Access 2003 doesn't have that error.
First i thought it could be a user account or permissions issue.. but i have checked with an admin account on the new PC and it throws this error:

Error 3079: The specified field 'Product Code' could refer to more than one table listen in the FROM clause of your SQL statement

Any ideas?

p.s. i have tried  reinstalling access 2003
0
jibranilyas
Asked:
jibranilyas
4 Solutions
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Nope.  Dump the SQL statement here.
0
 
jibranilyasAuthor Commented:
sorry, don't have access to that... i will c if i can get that for you...

anything that you can think ... after all, the code works in all but the new PCs.
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
If you don't have access to the SQL statement, then how exactly were you plainning on fixing this?
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!

 
peh803Commented:
The weird thing is that the statement "has been working for years" on other computers...

Typically, an error like this will refer to the scenario where a field name referred to in the select statement exists in more than one table and table aliases have not been used.  So, the rdbms gets confused and doesn't know which value from which table it should give you.


peh803
0
 
shanesuebsahakarnCommented:
Well, you could also try installing the Jet SP8 service pack, but I have a feeling that's not going to make huge amounts of difference. As Jim says, if you want to troubleshoot this, you'll need access to the SQL statement that actually fails.
0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:

  Check how the ANSI 92 option is set (tools/options, tables/queries tab) between a station that does work and one that doesn't.

  If they are the same, then put a copy of the database from a station that works onto one that doesn't.  If it still doesn't work right, then it's a problem in the environment (Access install).

Jim.
0
 
jibranilyasAuthor Commented:
thanks guys...

this is what i did....
being more of a PC tech, i was just curious why the same code would work on one machine and not the other when the database is same ( on the network drive )    with the ODBC connections identical as well..

Soo, i uninstalled access 2003 and installed access that came with office XP... now THAT works... i m delighted but then again... not a perfect solution...

now what i m gonna do is just upgrade access from access xp to access 2003.    FYI- one pc that was had the upgrade of access 2003 wasn't throwing that error as i mentioned in earlier post...

I will keep u posted.
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now