>I started with my current employer last March. I was hired to help maintain several FoxPro 2.6a DOS & Windows apps. The current plan is to convert those apps to PowerBuilder and I have been learning PowerBuilder as well as doing maintenance. I am not impressed with PowerBuilder. I think it would be easier and faster to convert these apps to VFP and forget PowerBuilder.
>
>Does anyone know of any VFP vs. PowerBuilder data? Any help in convincing my managers to convert to VFP will be greatly appreciated.
>
>Thank you.

Perhaps your company should consider migrating the app to the web instead of VFP or PowerBuilder. How many users are going to be on
the system? Are the users dispursed geographically?

Going from FPW2.6a to PowerBuilder you will find that FoxPro can do some things that PowerBuilder can not.

PowerBuilder; however, is marketed by Sybase whereas MS reps keep saying (as I read on this forum) that VFP is going away. I used to
dismiss those comments but I am a contractor and the demand for VFP programmers has dropped rather dramatically over the last two
years. Well, so has the demand for PowerBuilder. Reason: Much new work is being done on IntraNets and the web.

Going to VFP would be MUCH smoother than going to PowerBuilder - I have programmed large systems in both environments. PB has
some slick things such as the datawindow and built_in graphing.

The smoothest transition would be to VFP. The wisest might be to go to the web using ASP, VBScript, JavaScript, ADO, SQL Server (or dbf's
via odbc).

Good luck.
Carl