Many developers remained on SP1 for years due to stability concerns. However, SP2 introduced deep-seated changes in the following areas:

If your application is currently running on Visual FoxPro 9.0 SP1 and appears stable, the question is: move to SP2 or not?

Reasons to upgrade:

Reasons to stay on SP1:

In 99% of cases, upgrading to SP2 is the correct decision.

Microsoft Visual FoxPro 9.0 Service Pack 2 (SP2) is the final, cumulative service pack released for the Visual FoxPro 9.0 development environment. It represents the last official update from Microsoft before the product entered its extended support phase (ending in 2015) and eventual retirement. SP2 is essential for developers seeking stability, performance improvements, and enhanced compatibility with modern Windows environments at the time of its release.

Since Microsoft has ended extended support, Visual FoxPro 9.0 SP2 is considered legacy software. While it is still widely used in many industries for legacy applications, developers are encouraged to migrate to modern platforms (like .NET, SQL Server, or web-based solutions) to ensure long-term viability and security.

Visual FoxPro 9.0 Service Pack 2 (SP2), released in October 2007, holds a unique place in software history. It was the final service pack ever released for the product before Microsoft ceased development. For the "FoxPro Community," SP2 is not just an update; it is the final, stable baseline that all legacy applications should be running on today.

This article covers the key features introduced in SP2, the critical bug fixes it delivered, and the essential steps for a successful deployment.

SP2 updated the IntelliSense engine to better recognize new syntax and provided better support for handling custom scripts and complex object hierarchies in the code editor.

When distributing your VFP 9.0 SP2 application, you must include these core files (usually via an installer like Inno Setup or InstallShield):

Crucial Note: Never simply overwrite vfp9r.dll on a client machine without using the official installer or manually registering the COM components. A "side-by-side" installation conflict can occur if another application uses a different VFP runtime version.

Shortly after SP2, Microsoft released the Sedna add-on (an extension pack for VFP 9.0). Sedna requires SP2. It included:

If you plan to use Sedna or any community-supported libraries (like VFPX), you must have Visual FoxPro 9.0 Service Pack 2 -sp2- installed as your baseline.