>Yeah, I was afraid some one would post a reply like yours, :)
>but your comments are good and appreciated.
>
>The application is a Decision Support type of app where users want to start with a large data set and browse around and then drill down from there. This easy in Fox by just attaching a table to a Grid and
>So we will then need to re architect the app and present the user with more summarised data and cater for more drill down.
>
Well,
I was not the only one with doubts. Speaking mostly from the technical side of things,
the vfp approach of having large amount of data locally available makes some tasks easier.

The C/S approach has much going for it from safety and areas as well and the DotNet
mantra is the disconnected data set held in memory. Advantage allows you to access vfp tables
from Dotnet and might give a more vfp-like way of handling data in your Dotnet app.

But weigh the needs of keeping the same approach vs. a more C/S spirited one
not only on the structure of the current app. On some points the newer "biz models"
are miles ahead of the simple 1 tier vfp app (and IMHO better than simle MVC designs) -
it is just that MS missed a couple of other things in appreciating the use of local data.

At least recheck and perhaps rearrange the architecture of the vfp app -
otherwise IMHO a rewrite is only cosmetic and probably a waste of resources.

knowing that I am guessing a lot on almost no facts (see TC's post)

thomas