A user has an Access query that returns multiple items instead of just the item requested. The query works correctly on another pc. Could there be a corrupt file (dll) on his pc that is causing this? any help would be appreciated.
Thanks
Printable View
A user has an Access query that returns multiple items instead of just the item requested. The query works correctly on another pc. Could there be a corrupt file (dll) on his pc that is causing this? any help would be appreciated.
Thanks
Yet another toughie! Love floundering aimlessly. Are you sure the query is identical on both machines? I doubt that you have a dll issue. I would say you have a problem with the syntax of the query or the structure of the database.
Guess I could have put some more info into this. This is actually a simple query, pulling one piece of data - an org code -- from one table. Instead of getting only the code queried, five different ones appear. It seems that it just doesn't work right on his machine.
Can you post the SQL code ( go to SQL view and copy/paste)
Here's the code:
SELECT PROD_V_SITE_INVENTORY.NIIN, PROD_V_SITE_INVENTORY.UIC, PROD_V_SITE_INVENTORY.ON_HAND
FROM PROD_V_SITE_INVENTORY
WHERE (((PROD_V_SITE_INVENTORY.UIC)="W3142"));
And what does the uic column (on the multi-record machine) say ?
Does it show W3142 for each 'repeated record' ?
No it give various UIC numbers instead of just W3142. I don't think it's repeating records, its just returning more than those records with UIC of W3142.
Can you post the other UIC numbers that are returned. Your SQL looks fine. IS PROD_V_SITE_INVENTORY a table or a view ? I would look at the table using Design Mode and check the column definition. Got to be something overlooked - I haven't seen a corrupted DLL cause that sort of problem.
Could be squirrely string comparison problems as he is using "=" rather than a "like" operator. Sometimes this is enough to throw a Query off, depending on the references in the local mdb or mde file.Quote:
Originally Posted by Grateful_Dad
Been awhile since I posted here. but just found out that he was pulling data using an older odbc driver that was most likely corrupting the data. When I used the ODBC driver version 8, everthing worked fine. so I told him not to use the old connection anymore. So I think this problem is solved. I have another one I'll probably be posting soon.
:)
Thanks for posting back - thats how we learn