Hmmm, interesting. Okay, I would do this but how would I find out the name of the property to set? From the Microsoft Word help file it is not obvious what the name of the Word property was. In the code below I use "goWordDoc.SpellingErrors.Count", I only happen to know that one coz I got it off the MS web site.

>Maybe you should 'uncheck' it from within VFP? What if client desides to check it in the Word again?
>
>>I figured out what was going on. The darn client upper cases every single word in the comments field. And Microsoft Word, by default, is set up to ignore all upper case words. That is why I never got any spelling mistakes. So I unchecked that option from within Word and everything now works perfectly.
>>
>>>Take a look at the classed for spell check in the download section: file #1201, file #1122, file #9412.
>>>
>>>>I am trying to use VFP7.0 to do automation spell checking using Word 2000. I am running the code copied from Microsoft.com unchanged (Ref article Q271819).
>>>>
>>>>Problem: I keep getting the message saying "No errors found" even when there are errors in the text.
>>>>
>>>>The code in question is below and I have verified that goWord.Content.Text is being set to the correct string containing spelling errors.
>>>>
>>>>Thanx.
>>>>
>>>>goWordDoc.Content.Text = Alltrim(Thisform.pageframe1.page2.edtComments109.Value)
>>>>goWordDoc.Activate
>>>>If goWordDoc.SpellingErrors.Count > 0
>>>> goWordDoc.CHECKSPELLING
>>>>Else
>>>> =Messagebox([Spell check complete. No errors found],0,[Spell Check])
>>>>Endif