>>
This is the technique that we recommend and the way most solutions seem to be being built when XML Web services and VFP is involved.
>>

Question.... if VFP logic encapsulated in a COM component could be reasily replicated with the VFP Toolkit for .NET - and wrapped in a .NET Component - why wouldn't you recommend that? It seems to me that if the decision is made to go to .NET - then it makes sense to get as far into .NET as you can. If the VFP COM Components can be morphed into .NET Components with little work -what demonstrable benefit is there in keeping the VFP COM Components around?