Modifying Name AutoCorrect Options From Code

D

DBG

Hi-

I'm playing around with setting global options from code using the

Application.GetOption("") and SetOption syntax.

at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k/html/acglobaloptions.asp
it states that
Track Name AutoCorrect Info
Perform Name AutoCorrect
Log Name AutoCorrect Changes
are (.mdb only)

Does this mean that for my MDE these options will never be read / used and
as such I do not need to worry about turning them off? (there's a bug with
displaying landscape print preview)

Also, does anyone know how to access the key
ReplaceText for Spelling replace as you type? Its stored under the registry
keys for specific users and as such seem inaccessible.

Thanks,

-David
 
A

Allen Browne

David, I would assume that when the msdn article says "MDB only", it means
"not ADPs" rather than "not MDEs".

The spelling thing is part of Office, not part of Access. While it might be
possible to modify the user's settings, I'm not sure that's a great idea,
and it is not going to be effective if you install the runtime.

If you are actually trying to prevent the spelling AutoCorrect from firing,
you AllowAutoCorrect property of your controls to No_Obviously that should
be off for all combos, and for most text boxes (names, cities, ...
everything except for things like Comments.)

Just to be really clear, the spelling AutoCorrect is completely different to
Name AutoCorrect and it's attendant problems.
 
D

DBG

Allen-

Good to get a response from a real pro! Thanks.

Allen Browne said:
David, I would assume that when the msdn article says "MDB only", it means
"not ADPs" rather than "not MDEs".

Ok, this makes sense, I'll need to apply the property on open of my
application and toggle it back on close.
The spelling thing is part of Office, not part of Access. While it might be
possible to modify the user's settings, I'm not sure that's a great idea,
and it is not going to be effective if you install the runtime.

It's interesting, when autocorrect fires in the runtime you get the
lightning bolt. If you turn off the option, it affects the full version of
access but not word. As I comment below this is now a non issue.
If you are actually trying to prevent the spelling AutoCorrect from firing,
you AllowAutoCorrect property of your controls to No_Obviously that should
be off for all combos, and for most text boxes (names, cities, ...
everything except for things like Comments.)

Somehow I had managed to overlook (for quite some time) that control
property. Thanks for pointing out my problem, should be an easy fix to set
it off on the parts of my forms where needed!
Just to be really clear, the spelling AutoCorrect is completely different to
Name AutoCorrect and it's attendant problems.

Absolutely, I'm turning off name autocorrect to solve the associated
problems while the application is running.

Thanks again!

-David
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top