Two suggestions:

1. Chado has a RTF control with spell check which works well in VFP. http://www.spelleditor.com/ Fairly cheap and easy to use. Works against a memo field in a SQL Server remote view.

2. Sometimes it's just not worth trying to fight/reproduce Word. I have an app where I store the Word DOCs in a SQL table (image field). The remote view has a memo field. On demand I write the DOC out to a temp file (strtofile()) and open it with word. When the user saves the record, I save the doc in Word (if Word is still open), store the DOC file in SQL (filetostr(), tableupdate()) and deletes the temp file. The reason I decided I had to use Word for this app was it's page control/formatting advantages over RTF. (headers, footers, output options by page, etc)


>I'm working on a Work Order project.
>
>It is currently slated to be fat client. VFP front end - back end will either be VFP or likely SQL Server. Web front end, but the user base is via corporate intranet.
>
>I've used Web Connect before and am comfortable with its capabilities if you feel web based is a better way. (I see how slick UT continues to evolve with capabilities)
>
>Currently some users use a standardized Word DOC and email it to the labs doing the work. They are comfortable with Word because of spell check, font control, etc.
>
>Other users/labs use an early Work Order system I built in pure VFP a number of years ago. What's better about it is the data validation, better part handling, query and reporting.
>
>Now we wish to commonize.
>
>I'm thinking the backend will likely have to go SQL due to sheer size of work orders. Typically they run about 1/2 page in Word, but can go to 6-7 pages. 1000s are written each year.
>
>I like VFP as the front end for the attributes, validation and rich control/customization. However, I'd like to somehow allow the users to still use Word for the text portion of the work order.
>
>I'm not sure how to approach this, plus I'm a SQL Server newbie. Even if there was a good RTF type control that could write to the equivalent of a memo type field in SQL Server, that would be good. Spell check is a nice to have, but not a deal breaker at this point.
>
>Any suggestions or directions I should be checking for this project?
>
>Thanks,
>
>Peter