To answer your specific question, you cannot access one version's spell
checking with another (not via the RunCommand-tpe solutions).
Now I know this is a very unpopular opinion, but is one I have had since the
very first version of the runtime of an Access that had a spellcheck option
(Access Developers Toolkit for Access 95). If Microsoft wants to consider
spell checking to be a value add of the full retail version, then why work
so hard to circumvent it? Get the utility from FMS (Total Access Speller) or
have the clients buy the full version of Access, and be done with it!
If one works SO hard to to try to circumvent the intentions of a product,
then one has to ask themselves why they are using that product, seriously.
And one also has to ask themselves how they would feel about having their
intentions about their own applications circumvented by users who did not
like the given guidelines....
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
This posting is provided "AS IS" with
no warranties, and confers no rights.
"Dalan" <ot***@safe-mail.net> wrote in message
news:50**************************@posting.google.c om...
I did a recent post of the below and apparently no one had any
comments? Surely, someone would know if later versions of Office can
be referenced. Any comments would be welcomed. Thanks.
ot***@safe-mail.net (Dalan) wrote in message
news:<50**************************@posting.google. com>...
I thought that I would add an enhanced feature to an Access 97 runtime
db by including a procedure to allow the use of MS' spell checker via
a command button, so that users who have an Office app can speed their
spell checking efforts in lieu of using the add-in one. Well, it works
as intended, but with limited results. It seems that it is compatible
with Office 97 only. So, does anyone have any experience in being able
to utilize later Office versions? Any assistance will be appreciated.
Thanks, Dalan
Here is the code that I'm using that actually came from Q179318:
Private Sub Command0_Click()
If Not IsNull(Me!Notes) Then
Me!Notes.SetFocus
Me!Notes.SelStart = 0
Me!Notes.SelLength = Len(Me!Notes)
RunCommand acCmdSpelling
End If
End Sub