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 _______________________________________________ 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/[email protected] ** 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.
