You mean 'Hey, guys' (I think) - You're right - the foxISAPI that came with VFP 7 and the accompanying help - MSDN documentation - and samples seem to go back to VFP 5.

VFP/foxISAPI DCOM's do work. In process DCOM's work (at least as a 'localhost' service). I wish MS would get serious about foxISAPI. Every question about it seems to lead into discussions about 3rd party repackagings.

As you stated - it would be nice to know if the client breaks a connection with an in process (vfp) DCOM. MS is not [or so it seems] supporting us as it relates to foxISAPI. Rick's information is pretty good. There are 1 or two MSDN white papers - i think rick wrote those also! - and thats about it.

I noticed when I was trying to figure out a free MS internet control - few could respond directly to my questions . I was constantly being directed away from the free MS guy and towards other commercial substitutes. I stuck with the MS one - and you know what - it worked GREAT!

To many alliances and old relations seem to be standing between what we can do with foxISAPI and the effort MS will put into helping us understand and implement it!

>Hay gay’s, my problem is that I not found any clear information about FOXISAPI updated with the VFP7.
>
>The information I find is about the remote servers that we can satiate with FOXISAPI and the new run time for VFP7 components, specifically about threading (single or multi) with a multithread VFP dll and how MTS support it, if the persistent component verify and error it crash or no?
>
>Thanks for any information