You might also look into a .net framework as a way to get up and running pretty quickly on the data handling stuff. I've been using Strataframe and I'm very impressed with the Foxishness of their approach to data handling. Feel like it has flattened the learning curve dramatically for me. (that I am putting up my own money for licenses and training in Texas next month and am doing a bet-the-farm enterprise app with it later this year testifies to my sincerity in this <g> ) I found the whole .NET thing pretty daunting - with the kind of time differences on a rewrite you are describing - before I decided to go this route.

Hear good things about DevExpress as well - Cetin can speak more to that.


>The backend is gonna be SQL Server. The thing is that for a lot of companies it's not an issue of what is the best tool available, it's an issue that management has made up their mind about what tool to use based on marketing (supposedly the latest and greatests) so if they decide it's .NET somehow you have to get to .NET and I'm not saying it should be done in foxpro period, I'm saying that the road map could start with foxpro leading to .NET to save time and money but at the same time the whole thing can be started doing all .NET which if we had more .NET talent would be the way to go for sure, but the main talent here is Foxpro, so just wanted to see the cons/pros, in fact I haven't seen anybody on this forum that is doing a rewrite of an app (pressured to get it to .NET or something other than foxpro) mention this possibility, so am I the only one that has considered this? It seems that it's always straight to .NET, of course different companies have different scenarios and
>different talents but in a scenerio similar to mine why haven't they considered or gone thru this route?