Updating Label from textbox comparison but executing long query time

Access 2010
Userform  textboxes
sql 2012 backend linked tables

What I have:
Trying to update a Label after comparing to textbox values.

Running a dlookup in the textbox 86...but the dlookup is from a query linked into the Sql server 2012 tables.
Taking approx 3-sec to run.

If Trim(Me.Text1.Value) = Trim(Me.Text86.Value) Then
Me.Label88.Caption = "Compliant"
Me.Label88.Caption = "Not Compliant"
End If

I have put this in many property events.

Form Afterdate.

I finally had to put it in the GotFocus Event of the Texbox 86.

The query running is taking so long the comparison of the 2 textbox values are not updaqting the Label correctly.

Trying to get away from a user having to actually click in the textbox to get the correct calculation ?

Who is Participating?
FordraidersConnect With a Mentor Author Commented:
Thanks...its just a reporting userform.  Not a database form. I'am sure indexes are playing a role.

I will keep trying.
The code to compare the two values needs to run from three places:
1. The Form's Current event - this will display the message as you scroll to a new record.  Only run the compare if you are NOT on a new record.
If Me.NewRecord = True Then
    run compare
End If
2. The AfterUpdate event of the first field.
3. The AfterUpdate event of the second field.

When putting code into a control level event that depends on a second field, you have to consider what you want to happen if the second field is null.  Usually, that means that the user simply hasn't gotten to the second field yet and so you don't want to raise an error.  If this were validation code rather than a warning message, it would go into the FORM's BeforeUpdate event rather than the FORM's Current event because you would want to be sure that the code ran BEFORE the record was saved so you could prevent the save in the case of an error.

The Got/Loose Focus events are always the wrong events to use for this type of requirement primarily, because you don't want the user to actually have to tab/click into the control to trigger the code.

If the DLookup() is taking 3 seconds, something is wrong.  Make sure you have indexes defined on appropriate columns in the tables and make sure the query is not joining to unnecessary tables or doing anything else irrelevant.   Please post the query and give us some idea of the schema if you want advice on speeding it up.

Choosing the correct event is critical to accomplishing the task at hand.  Certain things could work in more than one event but there is ALWAYS a preferred event so your task is to learn what triggers each event and that will help you to understand what code goes where.  The most critical event of all is the FORM's BeforeUpdate event.  Without using it correctly, you can never effectively trap errors and prevent bad data from being saved.
FordraidersAuthor Commented:
FordraidersAuthor Commented:
All Courses

From novice to tech pro — start learning today.