>I am fairly new to VFP5, but I can't believe that in this day and age, one still can't do a spellcheck on an editbox whilst in a form.!! (Or am I wrong and have I missed something?)
>
>Does this mean that we are still almost where dBase III was is the mid 1980's? I can still remember having to dump all the contents of a dbf's memo fields out to a text file, open a wordprocessor to do all the spell checking, and then import it all back again. It seems that very little has changed.
>
>What is M$ case when it comes to Spell checking? Don't they want people running distributed applications to have correct spelling? Why can't we have spellchecking when running a form and editing a memo field (editbox)? In "computer years", I think we are still in the dark ages in this regard.
>
>Just my feelings. Any thoughts?
>
>Regards
VFP comes with a spellchecker. However, your license agreement prohibits you from distributing it with your application. The reason is that Microsoft licensed the dictionary from another company and that agreement prohibits developers from redistributing the spell checker.
You can use ActiveX Automation and use the spell checker in Word. However, it is kind of a hokey solution because Word needs to be visible.
The best solution is to get a third party spell checker available at
www.hallogram.com.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer