I am seeing behavior in an app for the same function that differs between systems running Windows XP and Windows 8.

We are using Craig Boyd's spell checker class straight out of the box - no modifications. The class is invoked from a VFP form, pointing to a text value to spell check. The spell checker runs, evaluating the text block and identifying any words it thinks are misspelled. The user may edit the word, ignore the word or select from a suggested list of replacement words. The class updates any word that is changed back to the text value on calling form. The class has worked flawlessly for several years.

We are now migrating to Windows 8 systems for some users. For the most part everything still works fine, but an odd behavior in the spell checker has shown up. When running on Windows 8 a misspelled word in the text block sometimes gets skipped. If another word nearby is trapped by the spell checker you can see the "bad" word in the text block being evaluated. The spell checker simply doesn't trap the word as misspelled (and I mean it is really misspelled - something like higeiorujdfnmhlight instead of highlight)

And, of course, the best part if this is that sometimes the word will be correctly trapped on the Windows 8 system.

When running the same exe against the same data in Windows XP the spell checker will trap this word every time.

The spell checker class uses doevents so this may be a clue. But I am at a loss to understand how the evaluation each word, moving from one work to the next in the text block, would be different between XP and Win 8. Clearly I am not looking in the correct place.

Hoping someone out there can show me the light.

TIA for your help,
Magaret