name auto correct

[Nona]

Can someone tell me why the name auto correct is not working on my database?
It was working before I split the database. Now it doesn't even though the
Tool settings are set for it and also the form I am using is checked for
allow auto correct.
I set the settings on both the FE and the BE, but it still doesn't work.

Thanks!

 

[Rob Parker]

Hi Nona,

I don't know why it's not working. But I, and most other serious Access
developers, would strongly suggest that you should always turn this feature
off for every database that you create - it's commonly known as "Name
AutoCorrupt" ;-)

See here for details: http://allenbrowne.com/bug-03.html

HTH,

Rob

 

[Nona]

Thanks for your reply. I only want the feature for spelling. Is it possible
to turn on the spelling feature and keep the other autocorrect feature turned
off?

On the form properties, it is checked to allow auto correct, but it doesn't,
even tho they are checked under the Tools/Option menu.

I will greatly appreciate your help with this.

 

[Rob Parker]

Hi Nona,

Sorry, I don't have a definite answer for you. The autocorrect feature you
mean is controlled by a setting (Allow Autocorrect) for the textbox (or
combobox) control itself; there is no setting in the form's properties, and
the option under Tools/Options (in the Name Autocorrect section of the
General tab) has nothing to do with the "spell-checker" autocorrect; that is
the "Name Autocorrupt" feature which you asked about, and which I responded
to - and which you should always turn off before doing anything else!!!

Perhaps the problem is due to a missing (or moved) dictionary file; or
perhaps you're actually spelling all the entries in the dictionary file
correctly. You could check that by entering a mis-spelling from the list of
words in the dictionary - which you can view via the Autocorrect Options
button on the Tools/Options/Spelling tab. If that doesn't work, then I'd
suggest you post a new question (with Spelling Autocorrect, rather than Name
Autocorrect in the subject line), since many people will probably not be
following this thread now.

Again, HTH,

Rob

 

[Nona]

Thank you for your thoughtful reply.

I think I haven't explained very well. The type of auto I want is for
editing names on a form. Before splitting the db, when a user, using a
filter, began to type in a name, it automatically populated the text box.
Under the filter by form, if she typed in "ja", she would automatically get
"jackson."

After splitting the db, it will no longer do that. even with the allow auto
correct under Options/Tools and the property on the text box in the form is
checked to "allow auto correct."

Am I barking up the wrong tree? Maybe this is not the auto correct feature
at all.

And why would this feature work before splitting the db but not after it was
split?

This is very confusing to me...I hope you can help me get it straight. Thank
you.

 

[Rob Parker]

Hi again Nona,

As far as I'm aware, that behaviour has never existed for textbox controls.
It does happen for comboxes, though. And the Limit To List property does
not affect it.

HTH,

Rob

 

[Nona]

Thank you for your help. I’ve learned quite a bit, even tho the autocorrect
still doesn’t work on the split database.

You sent a link to Alan Browne’s article about Name AutoCorrect, where I
learned that the NameAutoCorrect and the AutoCorrect for spelling are quite
different. So, I’ve turned off the NameAutoCorrect.

The autocorrect for spelling works perfectly in a copy of my database that
is not split. Using the filter and keying in the first couple of letters, it
comes up with the name we are looking for. According to the Microsoft Help
file, this feature is enabled for all text boxes and combo boxes in Form
view. It can be disabled via the object’s property settings.

However, this feature doesn’t work with the split database, even with the
exact same settings on both the FE and the BE. I would be very happy to know
what I could do to make it function; however, the database is working well in
all other ways, so I’m giving up on this at least for now.