At this point - I'm just going to have the users drop that OCX file on to their PC's. And, although I too would like to revamp the spell checker a bit - I just don't have the time to do any major overhaul of it now. I tend to work on this little App of mine (which I call Mr. TimeTracker - since the co. used to be called Mr. Software - if you can believe it - and they also have an app called Mr. AR - into which I will eventually 'push' the data from my App - but, that is on down the line a bit) in between projects for clients.
L8r! -K- -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Malcolm Greene Sent: Tuesday, July 20, 2010 12:56 PM To: [email protected] Subject: RE: A Spell Checker for a VFP EditBox? Kurt, We experienced similar OCX problems when we released our app outside our development labs. We ended up dropping the OCX entirely (pretty as it was) and writing a VFP form that displayed errors in context in a regular readonly edit box. Instead of color coding errors in context, we surrounded unrecognized words with '--->' and '<---' markers. Not as pretty, but effective. Its been years since we did this and I seem to remember the task of building the VFP form to display errors in context and allow users to edit/auto-correct errors took much, much longer than we originally thought. Good luck! Malcolm [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/289ea162f5642645b5cf64d624c66a14071a1...@us-ny-mail-002.waitex.net ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
