>It's been a long time since I developed in VFP. When MS dedcided not to support VFP any longer, I made the switch to C#. Since then I haven't really had my finger on the pulse of the community as I did before.
>
>
>My question is - what's the sense of folks out there? Is VFP still going strong? Are there alot of developers still writing new applications in VFP?

We are actually staring a new project in VFP. It appears we are the only ones that do this?

Originally we weren't planning to start a new VFP project (unless it would be a small solution), but the reason for this decision was based on the limited timeline we have to get this application into production and it is fairly complex, not regarding the overall functionality, but regarding the laws and regulations that need to be built in. With our VFP framework we can develop this in the required speed, while having it stable and error free at the same time.

One thing that helped us with our decision is that our framework has been changed over the past few years into a C/S 3 tier application that enables non-VFP developers understand and work with most parts of the code. No deeper knowledge of Cursors or Aliases, or Buffering or Tableupdates is required, this is all encapsulated in objects that have their corresponding methods and properties. There are of course places where you would create an index on a cursor and do some SEEK's to tweak out the last bit of performance, but the mainstream coding will be possible to be done by any smart person who has done some work in Java or C# for instance.

The bigger liability is the image of VFP itself, and of course that there will be no 64 bit version. By adhering to a good class design and separating the responsibilities, it will be possible in the future to re-write this application in .NET easier than do move now from FPW 2.6 to VFP.