OK, I watched the video, and the different debugging methods make sense to me, but every time I try to put in a break and then run the code, it asks for a macro name. This doesn't make sense to me...the code is directly attached to the search box.
Problem with Search Boxes
- Thread starter Heide
- Start date
I watched the video, and the terms make sense now, but applying them to my code is different. I tried adding breaks and a stop to the code to try it out, and it keeps asking me for the name of the macro. There is no macro - the code is an Event Procedure directly from the object.
I also read your comment about the AND not working at the beginning of the code...what is the alternative then, for narrowing down the results?
I also read your comment about the AND not working at the beginning of the code...what is the alternative then, for narrowing down the results?
Gasman
Enthusiastic Amateur
- Local time
- Today, 05:44
- Joined
- Sep 21, 2011
- Messages
- 16,505
You place a breakpoint in the code in that event procedure, then run the form as normal.
That will take you into that procedure and walk the code line by line with F8.
Place a Debug.Print of the filter string before you try and use the filter and see what it produces.
An AND is only valid for subsequent extra filter strings, NOT the first string.
That will take you into that procedure and walk the code line by line with F8.
Place a Debug.Print of the filter string before you try and use the filter and see what it produces.
An AND is only valid for subsequent extra filter strings, NOT the first string.
- Local time
- Today, 00:44
- Joined
- Feb 19, 2002
- Messages
- 46,818
The initial fetch brings down enough data to fill the form, the rest is fetched in the background, x rows at a time. It is possible that this wasteful behavior was altered in more recent versions of Access. Select a large number of rows, wait for the Y value to fill in in the navigation bar. Once that fills in, all the rows have been retrieved.
