In which language/database Visual Foxpro should be Migrated

Question

I want to know that how we can migrate the desktop application created in Visual Foxpro into any other database/language. Please note that the application is disconnected with internet. (As we can work without internet connectivity) That's a standalone application where currently the files of Fozpro are used.

Please if possible provide any migrating document.

Answer 1

Here is a demo of an application that converts VFP to Servoy: https://www.youtube.com/watch?v=8rUsMMLbcqY

I have never used these tools or Servoy nor do I have any financial interest in them - I have just heard other VFP developers talking about them.

Answer 2

As far as I know there isn't currently any tool that converts a desktop application written in Fox into another language. You can use the FoxPro wizard and upsize the databases into SQl-Server, but as far as the code itself you have to rewrite.

Answer 3

There are many "how" to, but I would go based on your development team skill sets. Having personally developed with Fox since it was FoxBase back in the late 80's to present, we are in the process of a full rewrite, but so too a completely disconnected environment need, and need to NOT have a "SERVICE" based SQL environment (SQL-Server, MySQL, Oracle, etc), we have chosen to use SyBase Database-Advantage Local Server. It is a stand-alone DLL that allows database connectivity, creation, insert, update, delete, triggers, etc. A download is available here.

Additionally, we are developing in VS2012 using C#.net, WPF using MVVM. But as others have stated already, there really is no "automated" tool to convert the app, and the only real automated upgrade is with VFP's wizard to upsize to SQL-Server. However, you could relatively easily use every VFP table and just do a

COPY TO YourTable.CSV type CSV

TO get a CSV file of all your existing content, then bulk upload into whatever table in whatever final backend you are considering. One other advantage of SyBase Advantage was that they decided to pick up the slack where VFP was being dropped by Microsoft. Their engine automatically recognizes the VFP file formats and pulls into their database format so you don't have to. This definitely opened a door for others in the VFP world for future expansion... They also allow support beyond the 2gig single file format too. That might be one benefit for you to jump-start your conversion.