>> So you wouldn't suggest using VFP and build a COM server for both projects? Then use DCOM on the VFP application to connect to the IIS/MTS server where the .dll's are?
>
>
>> What would you do, build two completely separate business rule applications?
>>
>
>It depends on what you need to do. I would not use DCOM over the Internet - it's just not a scalable option for anonymous users.
>
>For distributed apps I would build a front end that communicates with a
>Web server that passes through COM objects on the server.
>
>There are a couple of articles on my Web sites that demonstrate both aspects
>(accessing content over HTTP and running remote components in this case
>using XML messaging).
>
>http://www.west-wind.com/articles.asp
>
>
>The XML messaging article in particular addresses your particular question
>although your implementation may vary.


I guess what I was reading from the post was that the VFP application would be local to the LAN where the IIS server resided. Then it would be just a matter of connecting through DCOM via the LAN with the COM objects necessary to use the application.

The IIS/Internet project would use MTS, ASP, XML (And all those other TLA's) to connect to the server and process. Then you have one central location for all the business logic of the application.


Wayne

Wayne Myers, MCSD
Senior Consultant
Forte' Incorporated
"The only things you can take to heaven are those which you give away" Author Unknown