Heya -
can u be more specific about 'uses data over the internet' ??

I've seen a few paradigms where there is a VFP fat client on the desktop, with internet hooks back to some server for data retrieval and update, with tables on the workstation holding a 'semi-static' set of data for the user to work with.

Basically an update was performed each time the user logged in, and from there any time a change or insert occured by the user, the data was either batched up for xmit later, or sent in real time to the back end server.

so - tell some more???
mondo regards [Bill]
>I'm afraid that as I haven't actually used WebConnect I have really misunderstood things (probably because WestWind still has quite many articles on their site that explain how to use FoxISAPI).
>
>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)
>
>Thanks!