I still use VFP for a lot of more "personal" stuff here but they have basically set it aside as a major dev tool here. VFP7 is the latest version we have installed on our machines.

I just find it humorous that they see every application as being a web app. Some stuff just works better as a desktop app whether it's .NET or VFP. But I'm a good boy and do as I'm told. :-)

>
>Don't get me wrong. I still think Fox has a place in the .NET environment, especially if there's a lot of data munging going on. IOW, a bunch of different reports with different data groupings based on the same data set.
>
>For example, if the reports are for the same time period in SQL Server (or other backend), pull the data once into VFP. After that, either build the query string, or use SET ENGINE BEHAVIOR 70 with a query containing all the fields, to generate the result set. Then pass it back to .NET via XML.
>
>In my mind, this should scale significantly better, regardless if you're using COM Interop or a Web Service, than making < n > trips back and forth between the client and the server, or the client, Web server and the data server.
>