Controls w/ DLookup ControlSource endlessly recalculating in Windows 8 (Access 2003).

Posted on 2013-01-10
Medium Priority
Last Modified: 2013-01-15
I know that Access 2003 is not supposed to work with Windows 8 but I have found it does just fine with this one exception.

If I have a TextBox control with "=DLookup..." as its ControlSource, it just keeps recalculating endlessly when I open the form.  This never happened in Windows 7.

Any ideas on what is happening here?  The form where it does this is a continuous form so there are multiple instances of the control.  As it recalculates the control appears to flash.

Thanks in advance.
Question by:MitchellVII
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
  • +2
LVL 27

Assisted Solution

MacroShadow earned 2000 total points
ID: 38765068
I don't use Windows 8 nor do I use Access 2003, but you may want to try using Allen Browne's ELookup instead.

Author Comment

ID: 38765143
Thank you. I have tried ELookup and still get the same odd behavior.
LVL 27

Expert Comment

ID: 38765169
Sorry, I haven't got a clue to what the issue is.
Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.

LVL 48

Expert Comment

by:Dale Fye
ID: 38765192
Can you post the entire text of the DLookup( ) domain call?

What is the name of the control for which this is the source.

Why do you say Access is not supposed to work in Windows 8, I've not heard that.  Although I'm sure there will be issues with the 64 bit version of Office.
LVL 48

Expert Comment

by:Dale Fye
ID: 38765202
I rarely use DLOOKUP() as a control source. Generally I'll use the Form_Current event to populate the control and then if that control value is dependent on another control, I'll use the afterUpdate event of the other control to populate the value of the control that you are using the DLOOKUP for.

Accepted Solution

MitchellVII earned 0 total points
ID: 38765249
Hmmm, I think I have found the problem and a solution.

It seems that Windows 8 does not like DLookup (or ELookup) as a ControlSource but doesn't mind it at all in the underlying query.  Weird.

** MS is weird.  They say that Office 2003 will not work properly with Windows 8, but the individual components will.
LVL 61

Expert Comment

ID: 38766483
It seems that Windows 8 does not like DLookup (or ELookup) as a ControlSource but doesn't mind it at all in the underlying query.  Weird.

Just a word of caution... if you are indeed resolving this by placing your DLookup in the query behind your form, you very may well find that speed/performance is shot.

There are other ways to work around this that won't kill performance like DLookup in a query will... for example using a combo box to lookup the values needed, or maybe a custom function called from the control source.
LVL 58
ID: 38767685
Just to add to what Miriam said, use of a Dlookup() (or any of the domain functions) in a query is not a good idea because the query parser cannot optimize the statement.  Poor performance will almost always be the result (you can get away with it on small recordsets).

All of the domain functions represent a SQL statement anyway, which you can write directly in a query, so there is no reason to use them there.  Either do a join, write a sub-select, or use another query as a "table" in this one.

 The  Domain functions were only meant to be used in places where SQL statements are not (like a control expression).   As the others have pointed out, there are other ways to get around the problem you were having besides moving it into the query.


Author Closing Comment

ID: 38777602
I found my own solution but the ELookup solution was helpful.

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

AutoNumbers should increment automatically, without duplicates.  But sometimes something goes wrong, and the next AutoNumber value is a duplicate.  This article shows how to recover from this problem.
Traditionally, the method to display pictures in Access forms and reports is to first download them from URLs to a folder, record the path in a table and then let the form or report pull the pictures from that folder. But why not let Windows retr…
Learn how to number pages in an Access report over each group. Activate two pass printing by referencing the pages property: Add code to the Page Footers OnFormat event to capture the pages as there occur for each group. Use the pages property to …
Have you created a query with information for a calendar? ... and then, abra-cadabra, the calendar is done?! I am going to show you how to make that happen. Visualize your data!  ... really see it To use the code to create a calendar from a q…
Suggested Courses
Course of the Month13 days, 22 hours left to enroll

801 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question