Hi Victor,

>The issue of not supporting Foxpro is not because of license cost but rather one of infrastructure efficiency. This development environment as advised by Microsoft was not meant for developing enterprise-wide applications. Running a Foxpro program over the wide area network hugs network bandwidth over the WAN links. This causes slower access and response times not only for your application but other systems running on the network links as well. Foxpro was really meant to support applications over a local area network only.

They are right...



...if and only if they are talking about a FoxPro application that was meant to run on a local network and later ran unchanged on WAN's, as well. You can develop applications in FoxPro that run across a WAN, but it requires a different approach and many things that have been considered to be correct are suddenly doubtful. Most local network applications are not well prepared to run across the WAN. For example, they have a lot of tables containing an index on DELETED(), they might even display an entire table in a BROWSE window or grid. They might store temporary data on a network. They might open a table several times, and so on.

The easiest way to move an existing application onto a WAN is probably to use Terminal Server or similar tools, as this requires little work. In any other case you need to rewrite parts (or even the entire) application after identifying what exactly is causing so much data transfer.

Christof