>>Hi Guys.
>>
>>My boss was wondering, of those of us using FoxPro for development, how many are creating new software and how many are only maintaining existing programs?
>>
>>Ian Simcock.
>
>I'm currently consulting at Dow Jones, which has traditionally been a big Foxpro shop. I was brought in to fix a VFP app crucial to the business but any new development is in .NET. ( that is true both for DJ and me personally )
>
>But Bill Fitzgerald raised the crucial point : the backend for the foxpro apps is SQL Server and has been for 10 years. New development in VFP against SQL may make some sense if you already have in place a sophisticated framework written specifically for a SQL back end ( I use VFE and if the app I am fixing did not have that in place I would have rewritten it in .NET faster than I could fix what they had, which had the framework but didn't use it) but if you don't have vfp -> sql chops already at your fingertips, there really isn't much point ( IMHO ) in starting a new SQL backend app in VFP.
>
>As to new VFP against DBC/DBF - IMO that has very limited usefulness and I personally wouldn't do it and haven't done it for 10 years.

Absolutely agree. I haven't developed a VFP app using DBFs since before the turn of the century. I've had to work on a couple, but that only makes me want to convert them to SQL.

All my new development is in .NET and has been for the last several years. SQL Server, Oracle (yecch), and DB2 (hurl..) as back ends.

I do have some existing apps in the field that are VFP/SQL that I still maintain, but those will not be enhanced - only converted as the need arises and time permits.