Visual FoxPro End of Support: What It Means and Your Options

Reviewed by the DESSS engineering team

Visual FoxPro end of support happened long ago: Microsoft's lifecycle page shows extended support for version 9.0 ending in January 2015. Yet plenty of these applications still run invoicing and inventory, because they do their job. An expired date does not mean software stops working, but it does mean nobody at the vendor will fix what breaks. This guide sets out the verified dates for common legacy technologies and the realistic options. For help living with these systems day to day, see our application maintenance services.

What "End of Support" Actually Means

Vendors usually retire products in stages. Under Microsoft's fixed lifecycle, mainstream support comes first and extended support follows. Once extended support ends, security updates stop unless a paid extension exists.

Three things do not happen on that date. The software does not stop running. It does not suddenly become illegal to use. And your data does not vanish. What changes is the direction of risk, which rises gradually as new vulnerabilities go unpatched, newer operating systems drop compatibility and skilled people become harder to find.

Some contracts and regulations treat unsupported software as a finding in its own right, so ask your auditors and insurer how they view it.

Lifecycle Dates at a Glance

These dates come from vendor sources, read in November 2026 and linked at the end of this article. Always confirm your exact version and edition, because vendors revise these pages.

Visual Basic deserves a separate mention, since it has no end date. Microsoft's language strategy describes a stable language that will not be extended to new workloads, and it generally avoids adding new syntax. A VB.NET application can therefore remain perfectly supportable while attracting fewer new developers each year.

The Specific Risks of Older Technology

Visual FoxPro

FoxPro applications often store data in DBF tables on a shared network drive. That design brings its own hazards, such as index corruption after network interruptions and file-level access that bypasses application permissions. The runtime is 32-bit, and each new Windows release is one more thing to test. Skilled developers do exist, but the pool keeps shrinking.

Classic .NET and VB.NET

Retired Framework versions lack security fixes, and third-party libraries gradually stop supporting them. Moving from an old 4.x version to 4.8.x is usually a modest change. Moving to modern .NET is a larger project, especially for Web Forms and WCF.

Reporting platforms

SSRS and Crystal Reports estates tend to grow for years without anyone keeping a list. Hundreds of reports may exist, many unused. Since Microsoft will not release a new SSRS version beyond 2022, the sensible first step is knowing what you have. Note that Power BI Report Server usage rights depend on your licensing, so check that before planning a move.

Old SQL Server versions

Applications are often tied to a database version by compatibility levels, old drivers or deprecated features. An upgrade may well be easy, but you only find that out by testing.

Your Options

Most organizations have five realistic choices, and they can be combined.

Keep and maintain

This suits stable applications that rarely change and face little outside exposure. You need people who can support the technology and a tested recovery plan.

Isolate and contain

Reduce the exposure by limiting network access, placing the application behind a modern gateway, restricting accounts and monitoring activity. Isolation lowers risk without removing it, and you should record the decision and who accepted it.

Buy time through paid extensions

Programs such as SQL Server Extended Security Updates give you security fixes for a limited period. They are useful while a planned move is underway and poor value as a permanent state.

Upgrade within the platform

Moving to a supported version of the same product is usually the cheapest real fix. Think of SQL Server upgrades, .NET Framework 4.8.x or a supported SSRS release.

Migrate or replace

Rewriting or adopting a commercial product removes the old dependency, but it costs the most and carries the greatest risk of losing hidden business rules. Our FoxPro consulting page covers that platform specifically, and SSRS consulting covers reporting estates.

How to Decide

Weigh four things: how much the business depends on the application, how exposed it is, how often it needs to change and whether you can find the skills to support it. An internal tool on an isolated network with no changes planned can reasonably stay as it is for a while. A customer-facing application holding personal data on an unsupported platform usually cannot.

Legacy Technology Review Checklist

• ☐ Every application and its runtime, database and reporting versions are listed
• ☐ Each version has been checked on the vendor's lifecycle page
• ☐ Internet exposure and network access have been reviewed
• ☐ Backups have been restored and tested recently
• ☐ People who can support each technology have been identified
• ☐ Source code and build tools have been located
• ☐ Compatibility with the next Windows and database version has been tested
• ☐ Auditor, insurer and customer contract requirements have been checked
• ☐ Each risk has a decision and a named person who accepted it

Frequently Asked Questions

Is Visual FoxPro still supported by Microsoft?

No. Microsoft lists Visual FoxPro 9.0 under its fixed lifecycle policy, and extended support ended in January 2015. There is no later version. Applications can still run, and specialist firms can maintain them, but Microsoft will not issue fixes. Your risk depends on what the application does, how exposed it is and whether its skills remain available.

Can Visual FoxPro run on current Windows versions?

Many applications continue to run, but Microsoft does not support the product itself, so nobody can promise it will keep working. Test on the exact Windows build you plan to use, including printing, ODBC drivers and any ActiveX controls. Keep the installer and runtime files safe as well, and keep a tested recovery image for the working environment.

Do we have to leave SSRS now?

Not urgently. Microsoft says SSRS 2022 is supported until January 11, 2033, although no newer version will be released. Starting with SQL Server 2025, on-premises reporting consolidates under Power BI Report Server, so licensing deserves a careful check. Use the available time to inventory your reports, retire unused ones and decide where the remaining ones belong.

What is the cheapest way to reduce legacy risk?

Usually a few inexpensive steps come first: test your backups, restrict network access, remove unused accounts, document the system and upgrade anything that can move within its own platform. These actions lower risk without a major project. They also reveal how much the application truly matters, which gives you better information before you commit to a bigger investment.

Want Help Reviewing Your Legacy Estate?

Talk to DESSS about the applications you are concerned about. We can check versions, test compatibility and give you a plain view of which ones need action and which can safely wait.

Sources

• Microsoft lifecycle: Visual FoxPro 9.0
• Microsoft lifecycle: .NET Framework
• .NET Framework support policy
• Microsoft lifecycle: SQL Server 2014
• Microsoft lifecycle: SQL Server 2016
• Microsoft lifecycle: SQL Server 2017
• Reporting Services consolidation FAQ
• Visual Basic language strategy
• SAP Community: Crystal Reports