Fix the performance of DoCmd.FindRecord and the related CTRL-F GUI
Bind a form to around 10K records or so in a continuous form
Do CTRL-F to find some value you know exists.
Leave the default direction of ALL in place.
That's 90 seconds of your life you won't get back.
Change it to down or to up. If your first guess comes up empty change it to the other direction. That's three seconds of your life you won't miss. This is VERY, VERY BAD. Why should ALL perform so poorly?
This bleeds over into DoCmd.FindRecord SomeValue, acAnywhere which performs so poorly it should no longer be what the Control Wizards crank out for a button to find a record.
If JobID is what I am looking for I have had to replace
DoCmd.FindRecord Me.JobID, acAnywhere, , , , acCurrent, True
Dim rst As DAO.Recordset
Dim strCriteria As String
strCriteria = "JobID =" & Me.JobID
Set rst = Forms(stDocName).RecordsetClone
If rst.Nomatch Then
MsgBox "No such Workorder found.", vbInformation
Forms(stDocName).Bookmark = rst.Bookmark
Set rst = Nothing
This should not be necessary, but the performance of search degrades rapidly after 1000+ records come into existence on the bound entity both in code and in the GUI