Click here to Skip to main content
15,891,248 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
I maintain an Access app for a client who had it written over 15 years ago. We've upgraded it over the years and now it's running under Access 2010. One of the users today showed me a combo box that has been giving them problems. I checked it out and realized that it was auto-correcting anything typed starting with "FR" to "Friday" preventing them from typing things like "Freddie" or "Frought". At least making their work a lot harder anyway. I looked at the properties for the combo box and noticed an AutoCorrect option in the "other" tab of its properties. I was shocked to see that. Why the heck would anyone want that in an Access app??? And if it's there, why would MS make it True by default?!?!?!? Jeez. I swear they're a bunch of morons over there sometimes. I've looked all over in the options for the app and for an entire form and also online to see if there's a way to turn it off globally but can't find anything. Obviously I can write code to open up every form in design view programmatically and loop through all the controls so I can reset every textbox and combobox to false but I'm really hoping there's some easier way.

Thanks,

AR
Posted

If even you, who probably could look at the full source code, cannot tell "why the heck would anyone want that in an Access app", how can people who cannot see this code guess why one wanted it?

I understand that you badly need some resolution, but could you be a bit more realistic. Can you contact the original authors? If not, and the code is really bad and not properly documented, it could be possible that the value of this code is very low, if not negative. There is no such thing as miracle. There are many cases when people eventually had to write some project from scratch, despite the desperate attempts to reuse the code. If you really face "the bunch of morons" (I cannot be 100% sure, but think it would be reasonable to assume that you are right), you should also understand that trying to get something useful from such a "bunch" could be just a wast of time. If you face that, you should also face the reality.

Maybe you would be interested to know that the autocorrect feature was always problematic in Access? Please see: http://allenbrowne.com/bug-03.html[^].
I don't believe someone can help you with much more than that. :-(

—SA
 
Share this answer
 
First and foremost.... NOT "TRACK NAME AUTOCORRECT." I'm very familiar with that "bug". MS fixed it in Access 2003 and turned it OFF by default. You apparently didn't read my OP carefully. If you had, you'd know why I didn't post any code. The code has zero, zippo, nada, nothing to do with this issue. It's a property setting.

Second, the original author tragically died of cancer many years ago. But whatever. Not your concern.

Third, this was not a setting in Access 97 or Access 2000 AFAIK. It's newer. Access 2007 probably. If you still don't know which setting I'm talking about, open a form in design view. Click on a text box or combo box. Go to the "other" tab in the properties window. See the setting "Allow AutoCorrect". That's making use of the AutoCorrect library in Office. Nothing to do with what you are referring to. When it was added to Access, MS made it TRUE by default. It does NOT belong in an Access application. Hence the moron reference above. So the bunch of morons refers to the designers at MS, not the original author of this project. It's been up and running every day of the week for nearly 20 years and runs fine for the most part. It's not a matter of reusing code. And the issue I'm talking about isn't code. It's a setting bestowed upon us from MS.

Fourth, there are miracles whether you believe that or not. :)
 
Share this answer
 
v6

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900