Visual FoxPro to Real Studio Converter

There was a point when Visual FoxPro (VFP) was one of the best development tools out there.  Some would argue that it’s still one of the better ones.  Unfortunately, Microsoft has decided to move on and no longer update Visual FoxPro so this means that handwriting is on the wall and it’s time to find a new development tool.

CULLY Technologies has released a Visual FoxPro to Real Studio converter.  More info can be found at

This converter is open sourced so you can tweak it to suit your own preferences and fix any bugs you might find.  It converts VFP forms to Real Studio forms.  Converting the User Interface can be a huge time waster so I’m sure many will find this useful.

No converter is perfect and neither is this one.  It does not convert reports, menus and a few other objects.  It also does not convert any code.

We’ve looked at converters over the years and, honestly, I don’t think code conversion is worth the effort.  You could spend a ton of development time in coming up with a halfway decent converter only to still have to tell the end user they’ll have to go line-by-line to modify the code to suit the Real Studio frameworks.  At that point why not just rewrite from scratch to begin with?  The new to Real Studio developer will have to learn and use the framework anyway and I think giving them a crutch to help them bridge whatever language they’re coming from to Real Studio does them no favors in the short-term or long-term, in my opinion.

Kevin Cully of CULLY Technologies spoke about Migrating from Visual FoxPro to Real Studio (members only to view) at the 2011 Atlanta Summit.  It was an interesting topic as I have never done development in VFP.  I would love it if Real Software added some of the features of VFP into Real Studio.  Kevin is also speaking the 2012 Real World conference.

Conversion tools, while always flawed, are a good thing as they make some aspects of converting from one language to another easier.  This one from VFP to Real Studio should be fun to watch.

Are you a fan of Visual FoxPro?  What do you think its strengths are over Real Studio?  What about the other way around?


5 thoughts on “Visual FoxPro to Real Studio Converter

  1. I would like to say something positive about the AYB VB6 to RB converter (which by the way is free now I believe). While the converted UI code was too messy to get much use out of, many of the pure VB syntax routines converted over nicely and saved my a significant amount of work in the business logic section of my project.

  2. I bought AYB’s VB6 convertor back then. It was pretty good. I’d be interested in getting hold of it again though as my copy is tied (IIRC) to my netbook which is getting long in the tooth.
    Where can you find a download?

  3. I bought it as well, but is a free download now, here is the link:

    I think a few of the “Pro” features are turned off in this free version, according to Will, but it seemed to work the same as the version I paid for 3 years ago.

  4. Thanks for the link, this product deserves to be more widely known about, think I’ll post a link to it on the forum

  5. As a long time VFP developer and a relatively recent convert to RB, I found this idea of a converter for screens (windows in RB parlance) interesting, but probably a little late to the game. I’m sure there will be VFP apps out there for years to come, but those developers that could read the writing on the wall have probably already made the jump to another development system.

    I know many of them moved on to VS, but it just seemed like too much for our type of development. I am also just a little put off by the fact that MS has dropped VB6 and VFP without providing a migration path to a new platform. That is, unless you want to re-write everything from scratch.

    I’ve been working with RB for the last 2 years and I’ve created 3 apps that are on the Mac App Store and in the process of re-writing our bread and butter app in RB. Knowing what I do about RB (2 years) and VFP ( since the days of dbase II), the ability to convert screens without the ability to convert the code seems … well, impractical.

    I also think that converting the screens in RB is one of the most enjoyable parts of using the IDE.

    As a long time VFP user and developer, I didn’t think there was anything that could hold a candle to it. And while there are still lots of things that VFP does much easier than RB, I’m slowly but surely becoming a real fan of RB.

Comments are closed.