Dragan.

My issue was related to foxISAPI.

Before 8, my fixISAPI COMs could instantiate server side HTTP and XML objects. Now they can't.

Yet, my ASP script can do it no problem.

I never noticed any instability issues that were beyond the pale of any other instability issues I had to write work arounds for.

So why - if they are going to let VFP wither on the vine - would they go to all the trouble of tossing the COM instantiation feature? You would think that COM instability would be useful fodder for their argument to kill VFP.

It doesn't make sense - why put a bullet in a corpses head if it's already dead?:-)

We all expect M$ to play it's little games, and we've known for quite sometime as M$ morphed from a half decent tools maker to a back door man for the brain police. But why pay engineers to remove something when it's no big deal?

Ya know what I mean?:-)


>>You know me! I was fearing it was intentional and to help kill VFP by preventing VFP from competing with other back-end objects like ASP and ASP.NET, that can instantiate such objects. I guess M$ wants to protect us by dumbing down our code on a par with their NET boiler plate shops in New Delhi - how - how - egalitarian of Microsoft. They're saving us from ourselves - and their stock value certainly shows they've been making good decisions, in this regard, for the past several years.
>
>I think they discovered two things: a bug and a lack of resources to fix it. What do you do with a faulty electrical outlet that you don't have the time to fix? You tape it over.
>
>Anything that follows from that is accidental. If it fits a larger scheme, good for the scheme.