>>Even though I have not done anything with Web Services, instinctively I believe that what I need for this new project is Web Services. So I wanted to ask some general design questions on how to work on this.
>>
>>First, let me describe the existing situation.
>>
>>I have an ASP.NET app that resides on a customer Intranet. This app. communicates with VFP app by way of calling Stored Procedures in VFP database. That is we use VFP Ole Db.
>>
>>Now I have a situation where a customer wants to put the ASP.NET on Intranet (they want me to find a hosting site and so on). The situation will change, the VFP DB is no longer within a network so I can't have the ASP.NET pages call VFP Stored Procedure. So I am guessing that the ASP.NET app will have use Web Services to send the info and get the info from VFP app (installed on some file server in the company network).
>>
>>My first question: Is this conceptually the right approach.
>>
>>Other questions. If Web Services is what I have to use, some very naive questions:
>>
>>1. Does it mean that VFP app has to run all the time to make sure that ASP.NET pages can communicate with VFP database?
>>
>>2. The PC where VFP app is installed needs to have Internet connection, right? If it is only DSL or Cable modem (and not T1), will this slow down communication considerably?
>>
>>3. Where do you recommend to start on this? Any articles, white papers, etc, would be greatly appreciated.
>>
>>Thank you.
>
>Hi
>Intranet is = Internet, but for in-house using
>You have to install only your VFP files on web-server
>HTH

I don't think this is applicable here. The VFP files have to reside on the data file server so that VFP application can have easy access to it.
Thank you for your suggestion.