But this is problematical in that it doesn't take effect until Access is closed then opened again. If someone should manually change the setting on a given machine, in any module of MS Office, it would have to be reset by your Access app again, once again being closed and reopened to take effect.
Hey, thanks ! it worked for me in Access 2010. By creating a macro called AutoExec with the instruction RunCode and passing it the name of the function (inside a module) that has your code.
Jump ahead 10 years to Access Microsoft 365.
Open up the database without even opening a table.
Top row Select Database Tools
"what do you want to do?" type OPTIONS - hit enter
Select Client Settings->Default Find/Replace Behavior
Select the General Search radio button
Press OK.
You have changed that default that not everyone would choose. AKA -driving them nuts!
Last edited by RaceShooter; Dec 29 '20, 05:26 PM.
Reason: misspelled word
RaceShooter:
You have changed that default that not everyone would choose. AKA -driving them nuts!
That's a very valid consideration - especially for changing options in code of course.
However, in this case instructions are offered to allow the user to make the choice consciously and with full awareness of what they're doing. If they don't like it then they simply choose not to do it.
The OP (Original Poster) has asked for help in order to make this change. The help was provided for them. It may also help countless others looking for the same thing. Anyone who chooses to follow these instructions, in spite of not actually wanting the same setup, needs help far beyond the scope of this website to handle wouldn't you say?
Comment