Hi Rick,

>Do you think they can't fix it because they haven't even identified the "real" problem yet. I would count on this link disappearing when they figure out which circumstances manifest this problem.

As I mentioned in one of my other posts on this thread it's connected directly to the OS. So it's more than just a VFP fix, since it works right under automation servers compiled under NT. So right from the start, it's a pretty complex issue in my estimation.

I doubt if the KB article will go away any time soon, however. There are still KB articles regarding FPD/FPW and Win 3.1.