Does AutoCorrect work in Access 2007 Runtime without Office Installed?

FWIW,

You will find that a great many DBA's do not use these features.

In some abstract theory, the database contains data, not Sentences of Paragraphs (that require Spellcheck or Autocorrect)
SQL Server
MySQL
Oracle
... none of there "Real" Industrial strength databases contain either of these features natively.


For example: is McBlain a value you want spell checked?
If it is not a common name, then it will be flagged by spell check, until it is added.

Do you always want "McFarlen" *Always* autocorrected to "McFarland"?.
Suppose you have both names?

Suppose you have an industry specific tern that resembles another word.
Do you really want these values "Autocorrected" (Remember, this is sometimes not even noticeable to the user) to the *wrong* value?
My last name is constantly being misspelled because of issues like this:
"Coachman" becomes "Coachmen"
:-(

The theory says that you should have dropdowns for certain values (States, Countries, Industry specific terms, ...etc), that are just not applicable, or even practically handled by Spellcheck or Autocorrect.

In other words, you should not be entering the customers name, because the name should be in a combobox linked to the correct spelling in the Customers table.

If you have some actual "Readable data" you are trying to insert into Access, you might want to spell check it in a word processor first, or Link to it.

This is all FWIW, and from what I have read, this is why these features are Not included in the runtime.
(Because the Office Dictionary is shared among all office Applications, hence any settings in the Dictionary may wreak havoc in a *Data*base.
Conversely, any custom settings made in Access may result in similar conflicts with applications that Spellcheck and Autocorrect were meant to work in.

In case I am not understanding your possibly unique situation, can you post a scenario where you need to use Spellcheck and Autocorrect in a database?

Thanks

JeffCoachman

Hi Jeff,

Thanks for the comments.
We run a survey database which has many multiple choice questions and also a vast selection of Verbatim comments which correspond. 99% of the words taken down are in the dictionary. It's rare that we type names.

We employ typers that can type fast and often there are mistakes (spelling and grammar).
We obviously need to keep the highest level of service for our clients while keeping the fastest time to complete each survey (which would mean not spending ages checking your work).

I appreciate that Runtime is free, however on my machine with All standard MS office applications, spellcheck works and autocorrect works in access runtime.
On a machine which doesn't have office installed (which will be the case for our new machines) spellcheck doesn't work, and I need to find out if autocorrect does/doesn't.

Hmmmm... this makes sense, however the autocorect feature doesn't necessarily link to the dictionary.
The reason I say this is because I can add an entry to the dictionary and an entry to auto correct which are completely indipendant of each other.

However... Just spoke to our computer supplier who says we have a machine ready to test and Autocorrect doesn't work.

I will award you the points because you are correct for the question, but are you able to provide any advice or links to anything which will help out with this?
I can only assume that 10 - 15% of all incorrect words which our typers have, are corrected by auto correct. This obviously takes time to fix when reading through the comments which have been typed.

Any help would be fantastic.

Can you explain again, exactly what type of data specifically, the typists are entering?

customer comments.
It's a call centre.
They ask the customer questions about a recent purchase and note down anything they say.

Then if it were me, ...I would leave this as text (with any mispellings.)
If I needed "precise" data in a report of some kind, I would export this data to Word.
Then do any Autocorrect and/or Spell checking there.

Either that or convince the client that if "They" need these features, then they may need to just bite the bullet an buy the full version of Access/Office.

You also have the option of running the Full version on Citrix, VPN, RDP, ...ect , if licensing is an issue

;-)

JeffCoachman