I am tasked with updating a program from VFP3/5 to VFP6, and I was thinking that I could use a VFP6 front end with VFP6 DCOM .EXEs holding all of the data-manip code (data to be moved to Oracle). I was thinking that DCOM would be better for LAN and WAN clients since no "heavy" code is running on the server and the network traffic is nil except for when the client writes a record or populates a view.... Are you saying this is a no-go for WAN clients?

Also, I was thinking of playing with DCOM over HTTP in NT4; I thought the text in http://msdn.microsoft.com/library/backgrnd/html/cis.htm says it can be done under NT4.

?



>DCOM, however, once connected can be very efficient. But it also requires a persistent connection to the server (or else you get the overhead of a reconnect each time which is dreadful).
>
>In general I think DCOM is not a good choice for anything but distributed components that must access content on remote machines on a fast network. For remote connectivity of application clients - there's too much baggage in terms of security, network administration and installation involved to make it really a good choice.
>
>DCOM is supposed to be able to run over HTTP in Win2000, however, I haven't looked into how and if that actually works.