Who told you it's not going to be supported??? Who told you not to use it???

Fortunately over here in DHAP we have some managers who actually listen to us ( developers ) as experts in what we do.

We try to use the tool best suited for the job. We have applications in VFP, VB, ActiveX controls in VC++, SQL Server, Access ( gag :-) ) and Outlook ( I'll never write another one on that platform tho :-) ). We use VBScript, Javascript, HTML, DHTML, etc. There are some in other branches here using ProblemBuilder ( gag :-) ) and SilverStream. The point here is to analyze the requirements and apply the right tool to the need.

Some of the smaller applications here are ideal for VFP. We have one multi-user app ( my first in VFP3 ) written about 4-5 years ago which was migrated to VFP6 and it just runs and runs, very few problems and when they have occurred, more than not it was caused by network related problems. And they are asking for upgraded features now.

For most larger applications we are moving more to using SQL Server for the backends. One we are currently working on uses SQL Server for the backend, VB for the presentation and middle-tier components of the app and VFP/Web connect for the middle-tier web parts.

I use VFP COM servers a lot for Intranet web related apps ( along with FoxIsapi formerly and Web Connect now ) because of all I can do with it.

I am trying to keep an open mind about using various tools and spend some time to learn them. That's good for me and good for the client.

Bill

>hewy Bill,
>
>Do you mean to tell me that some areas of CDC still opt to use Foxpro even though it's not supposed to be supported by MS in the next coming years? At least that's what they are telling why to use vfp.