One of my customers has a VFP 6.0 distributed application that enables agents to calculate policy information and then forward it to the central office on a monthly basis.
They would like to put this functionality onto the WEB (they already have an web site maintained at the central office). They would also like to use the calculation code in the current VFP application.
Two options are being considered:
1. Develop an ASP.NET application; web pages that would call a VFP COM .dll to execute business logic. (calculate, etc.)
2. Develop a VFP server application using Wconnect tools (from West-Wind tech.) to process web requests; generate web pages and perform the business logic.
Has anyone used both approaches? What are the pros and cons of each? Are there performance differences between them??
Thanks
They would like to put this functionality onto the WEB (they already have an web site maintained at the central office). They would also like to use the calculation code in the current VFP application.
Two options are being considered:
1. Develop an ASP.NET application; web pages that would call a VFP COM .dll to execute business logic. (calculate, etc.)
2. Develop a VFP server application using Wconnect tools (from West-Wind tech.) to process web requests; generate web pages and perform the business logic.
Has anyone used both approaches? What are the pros and cons of each? Are there performance differences between them??
Thanks