>I need to build a desktop application that uses data over Internet. If I were to build a system with browser based UI then I'd understand that using WebConnect is the best choise.
>
>My question is why should I buy WebConnect instead of using FoxISAPI. Even if FoxISAPI is not supported anymore - it should still be usable? The problem is that I don't want to go for WebConnect unless I'm absolutely certain that it offers significant benefit.
>
>DCOM or COM+ is just another possible solution that came to my mind. I could just put some application logic on server and use DCOM to exchange data.
>
>The last solution does seem cheaper but are there any hidden dangers? (e.g slower performance)

WebConnect, may or may not be the best solution. It is the one I use.

There are other choices, (read what Claude shows in this thread). That is also an excellent choice. Others are
- Active FoxPro Pages: http://www.AFPages.com
- FoxWeb: http://www.foxweb.com

Take a look at Rick's documents on how to do a desktop app (Fat Client).

You could also use plain old ASP or the newer ASP .Net
There are many choices to do what you want.

Also:
http://fox.wikis.com/wc.dll?Wiki~CategoryWebDevelopment

FoxISAPI and DCOM (slower performance)>. Not really. But a lot more complexity and headaches. Why go there?