Dlookup working on some computers

sad92027

New member
Local time
Today, 08:47
Joined
Sep 29, 2010
Messages
8
I have an Access2003 database that is split with a backend on one logical drive on the server and the frontend on another logical drive. I am connecting to a sql database on another server. I created an ODBC datasource on each computer for the sql database. I have a textbox on a subform that retrieves a value from the database using a dlookup formula. The dlookup works on my computer but does not on other computers. On the computers that are not working there is no error it just does not show a value in the textbox. Why would a dlookup not work on some computers but works on others using the same logon to the database.
 
Here is the solution to my problem. I realized that my computer has service pack3 for Access2003 and the computers that were not showing any result for the VLookup did not have the service pack. I installed the service pack on those computers and the vlookup worked properly.

I had another similar but slightly different problem on a new Windows 7 computer. It was not connecting to the sql server. The front-end access db linked to the sql server but when the links were created I was using a 32 bit driver. On the windows 7 computer a Sql Server driver was presented as an option but it ended up being a 64 bit driver. The use of that 64 bit driver is what caused the error when trying to connect to the Sql Server. If you go to C:\windows\sysWow64\odbcad32.exe and run it then you will see the 32 bit versions of the ODBC Data Source Administrator Wizard.
 
Don't know whether this is a typo or not but be aware that DLookup() and VLookup() are not one and the same! DLookup() is a native Access Function while VLookup() is native Excel. You can use VLookup() in Access, but I believe you have to load the specific Library that contains it and other Excel Functions.

BTW, SP3 for Access 2003 has some bugs! Make sure you have all Hotfixes for this Service Pack installed!

At any rate, glad you got your problem fixed!

Linq ;0)>
 
Last edited:
Hi Missinglinglinq,

Yes, it was a typo. I had solved the problems several days before posting and in the meantime I was working on an Excel spreadsheet with Vlookup formulas so that was what was on my mind. Thanks for the info on the hotfixes I will have to do that.
 

Users who are viewing this thread

Back
Top Bottom