I use MS Access (Windows version 2003 nevertheless ) for handling my significant lists such as my stock list for my eBay store. I deal mostly in one-of-a-kind products so that I have, over time, over one thousand listings. This is a lot to keep an eye on.
I needed a great way to look for and find things in a variety of fields. You may use the”[control] + f” keyboard shortcut, or you could use the Edit | Locate menu, to hunt, but accessibility defaults to match the entire field and you need to alter it if you need something else. I typically don’t want Match entire field. I normally need Match any part of area ipucum.
Some people like to use keyboard short cuts. I am more of a mouse man if there’s a one-click means to do something. If there’s just a many click way which goes through menus, even with just two clicks like Edit | Locate, then I will usually resort to pressing [control] + f. However this guide isn’t about whether one method is much better than another; this guide is all about offering another way to search using an Access database type.
So, I have developed a little button system that I use to locate things in a particular field. I set the button to the right of this area that it works on. I am able to get into the find dialog box setup how I want it with a single click.
I add the button in form design using the button tool. If you choose the Record Navigation | Locate Record action (a logical choice), then the wizard gives you the following code (we will change the code later):
The first line, Screen. Previous Control. Set Focus is fine. It sets the focus of what area will be searched to the previous field you touched. You could have one button for all hunts in this manner, however you’ll need to first click a field and then click on the button. That’s two clicks rather than every user may understand that’s the way it works.
The next line, DoMenuItem, is specific to each version of Access and means, in this instance, the tenth item in the Edit menu. You would need to change this for each version of Access.
If you choose the Record Navigation | Find Next task rather, the wizard gives you the following code:
The Find Next winipucu is far better than the Do MenuItem since you don’t have to alter the code for each version of Access. The dialog box that comes up when you click on the custom button in this guide includes a Find Next button, which means you really don’t want two buttons, Find and Find Next. Find alone will do well.
The accessibility wizard coding is fine but you don’t have any control of these parameters for your search. I dislike having to place the game box from match entire field to match any part of area after I forget and I’ve already searched using the entire field and can’t find what I know should be there.
I had a way to search each area with a single click, so I picked a button to do it.
I have multiple fields where I would like to have the ability to search. I did not need to write the same code over and over for every area. If I find a better way to code it, then I must recode every instance of the old code. Having one procedure is significantly better.
My button sets the attention of the search into the 1 area to the left of this button and then it requires one procedure to populate the locate command. Each button on the form sets the focus to the area at its left and requires exactly the same, 1 function to execute the search.