Never hold yourself to one platform. I think VFP is an absolutely wonderful tool, but I do not suggest it to every client because every client is different.

I do think that vfp is your better choice for datacentric apps, but your database does not have to be vfp. It could be sql server, etc.

I still am not interested in writing a data application in .net when I have vfp at my disposal.

Also, you should think about the pieces of your application where you might look at using another platform - say reporting? You could use asp.net to create a generic reporting interface and deploy it to all your users where they can access it on their browser. A reporting interface would not necessarily need the rich level of control that you need in a data entry application - where you need to enforce rules for data, etc. You could also build in automatic functions where the users could fax from the web, produce pdf's, etc.



>I'm sure this debate has been had a thousand times, and I've always been secure in our descsion way back in the days of VFP3 and Delphi1 That VFP was the ideal langauge for us.... BUT.....
>
>I recently chatted to a fellow developer who has a) been to the Foxpro Devcon and had b) come away feeling that anything new he did had to be in .NET because Foxpro was on its way out, maybe not for a year or three but the "writting was on the wall".
>
>Since I was not at DevCon I can't say how he reached this conclusion, but as we are just about to start a whole new project with no history, should we been looking at .NET instead of VFP?
>
>I know many of you will say "that depends on the application" but once you start down a track it's not often able to change. Initially this will be a datacentric application on standalone PC's or small networks. But who knows? Web Access?, hand helds? if it's successfull there may be many possibilities and a re-write would not be invisaged in the next 5 years. So is the fox slowing down? should we be in the .NET?
>
>
>Gary Williams