‹ BackHN Continuity

Thread

Microsoft killed FoxPro in 2007. Anyway, here's FoxPro revived

487 points · 270 comments · boredjohnny

  1. rufugee · · focus · HN ↗
    We run 500 KLOC of FoxPro at my company, daily. It is the engine that fuels a $500M business.

    I hate that it's the hand I'm dealt, but aside from AI rewrites (underway), there's no good answer. It's complicated by our reliance on DBFs.

    I welcome efforts like foxscript and anything else in this space. There are still a significant number of FoxPro apps out there and no one has a good answer. If you are struggling in this space, leave a comment here. I'll reach out to you. Strength in numbers...

    1. boredjohnny · · focus · HN ↗
      Hi Neat! you mentioned you guys are already on a rewrite path. That is the proper way forward and I recommend gathering as much information about the product and edge cases as possible. Document every business rule, every product decision. Handwaving aside, audit the Foxscript source code, clone it to a virtual machine or container. Any issue you face, feel free to post an issue on Github as I would love a few edge cases on the wild. As the Foxscript runtime relies on 64 bit offsets for the DBF/Memo, once a DBF (past the 2GB) is opened they can't be migrated back to old VFP9, so I recommend to test this carefully on an airgaped setup with tests DBF.
      1. rufugee · · focus · HN ↗
        Do you do consulting in this space? I'd be interested in having some discussions...
        1. boredjohnny · · focus · HN ↗
          I run a small consulting shop with a family member. We are a little bit tight on time but I'm willing to help with whatever you guys are facing rn.
          1. rufugee · · focus · HN ↗
            Would love to have a conversation. Drop me an email at rufugee@proton.me. Looking forward to it.
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.