Based on a private request, I will add my 2 cents.

The one option you can knock out is VB/SQL. If you are going to consider VB for the first time, VB .NET is the choice to make.

At this point, I assume you have a pure VFP solution (VFP App and VFP Data). The easy one to tackle first is the data. If the data requires the services to go to SQL Server, then you should not hessitate to transition your data to SQL Server.

Finally, we are left with whether you should stay with VFP or go to .NET. I would not recommend dropping VFP in favor of .NET. If you have an application in VFP and it works, then I would suggest sticking with it if you can, taking this time to learn .NET.

On the other hand, if you need to go to SQL Server, it may necessitate an overhaul of your VFP code. If you need to undertake a re-write of the VFP app, then your decision gets a little more difficult. I think part of the decision turns on whether you are a consultant or an employee. If you are an employee, you need to consider the needs of your company. The sensitivity to the current VFP situation is a little less sensitive. If you are a consultant, then your situation may be little more perilous. Based on your profile, I assume you are an employee. Still, as an employee, you need to be concerned with investing in a skill set that is going to have a long term payoff.

If you need to re-write the VFP app to work correctly with SQL Server, your company needs to evalutate that investment in VFP carefully. If your company values the idea of developing in tools that will be supported AND innovated, then you need to consider VB .NET. Finding employees to work on the application is another important consideration. As time goes by, it is getting harder and harder to find VFP developers. As others have said, keeping productive (ringing the register!) is important as well.

The wildcard in your scenario is SQL Server, because if you need to go to SQL, the impact on your VFP app may be such that you will have to re-write the app.

So, what are my recomendations????

If you need to go to SQL Server, then:


1. If you can get SQL Server weaved into your application in the short term (6 months or less), then VFP/SQL may be a good choice.

2. If you find that you need SQL Server, but it will necessitate a complete rewrite of your VFP app, unless you can do it within 6 months, then VS .NET should be considered.

3. If you don't need to go to SQL Server, stay with VFP but at the same time, invest in your VS .NET learning endeavors.


I don't know the particulars about your shop (size, ability to learn new technology quickly, SQL Server expertise, etc.). If you need to go to SQL and you are new to SQL Server, then maybe sticking with VFP is a good alternative since you will be minimizing the tools you have to learn. For sure, if I were in your shoes, I would need to consider the goals of the business, my personal goals, and juxtapose that with the current state and likely future state of Visual FoxPro. Regardless of your situation, you should be checking out Visual Studio .NET now. The degree and pace you get into the tool will depend on the outcome of the analysis enumarated above.

Good luck and best regards,