Latest VFP Version

[dylim]

Hi Guys,

This is the version of Visual Foxpro I have been using for the longest time:

Visual FoxPro 09.00.0000.7423 for Windows

Is this still the the latest?

The reason I am asking this is because I came across this link from Microsoft:

Download Visual FoxPro 9.0 Service Pack 2 Security Update from Official Microsoft Download Center

A security issue has been identified that could compromise your Windows-based system running Visual FoxPro 9.0 Service Pack 2. You can help protect your computer by installing this update from Microsoft.

www.microsoft.com

Should I download and install the above? And what will be the resulting version?

Thanks for your guidance, advise and enlightenment.

 

[GTGeek88]

Lurking . . . because I don't remember hearing about this one . . .

 

[gbcpastor]

The Service Pack 2 was the final update to VFP 9.0

It repaired several bugs and yes, it is a good thing to download and install.

Great question.

 

[Joe Crescenzi]

The 2024 date is what's interesting. Now I'm curious. I'm wondering if they just moved the Service Pack or actually did a patch.

The KB it referenced is a broken link, and the Security Bulletin is over 12+ years old, so I'm guessing it was just moved and they posted a new date.

Either way, I'll try it on a Virtual Machine I use for testing and see if the version number changes, if not, I'll roll back the VM so it stays as it was before I try it.

 

[dylim]

The Service Pack 2 was the final update to VFP 9.0

It repaired several bugs and yes, it is a good thing to download and install.

Great question.

What version number does your VFP install have sir?

 

[dylim]

The 2024 date is what's interesting. Now I'm curious. I'm wondering if they just moved the Service Pack or actually did a patch.

The KB it referenced is a broken link, and the Security Bulletin is over 12+ years old, so I'm guessing it was just moved and they posted a new date.

Either way, I'll try it on a Virtual Machine I use for testing and see if the version number changes, if not, I'll roll back the VM so it stays as it was before I try it.

Yep, 2024. Very unlikely of Micro$oft to give us a new patch for VFP.

Please do sir. Keep us posted. Thanks in advance!

 

[Joe Crescenzi]

Confirmed. The only thing that changed is the date of the web listing.

Inside the MSI are the following files, which are dated from 2012.


The end result is the same

 

[dylim]

Confirmed. The only thing that changed is the date of the web listing.

Inside the MSI are the following files, which are dated from 2012.
View attachment 2136

The end result is the same

Hi Joe,

So the latest version is still this?

Visual FoxPro 09.00.0000.7423 for Windows

Right?

 

[Tore Bleken]

Yes, 7423 is, and will always be, the last version.

 

[dylim]

Yes, 7423 is, and will always be, the last version.

Thank you sir.

By the way, have you tried out that VFP "Advance", aka VFP 10? Should we?

 

[Tore Bleken]

No, I have not used it.

I have seen it demonstrated several times, and I will see it presented once more next week, at Virtual FoxFest. But the reality is that I have never had any reason to switch, and I don't expect anything to happen in the future that will make me change my mind.

I recommend that you read Rick Strahl's comments about it, you should read the whole thread: https://support.west-wind.com/Thread5YZ172FPW.wwt#5Z40XEG0T

 

[Joe Crescenzi]

I'm neutral about VFPA. I made several payment as donations to support the developer because I like the idea that if Microsoft ever follows Apple's lead in removing support for 32-bit (which is VERY unlikely), I'll still have a way to deploy my code.

That said, if I decide to do a test with a real customer, there are still some things that are worth exploring.

1. He removed the 2 GB limit.

2. There are certain parts of Windows that are not fully supported by 32-bit applications. The best example of this is how printing is not as seamless as it used to be. The print dialogue doesn't always default to the orientation in your .frx files, so users often need to change the orientation manually and the Windows print preview window isn't supported for 32-bit programs.

3. He claims to have fixed a lot of Microsoft's bugs, most are minor, but this is encouraging. I suggested he address the SMB file corruption problem a few years ago but he said he wanted to address other issues first. If he fixed that bug, it would've given me a reason to take it seriously, but as it stands now, I have no reason to risk using it in a production environment for a few minor bug fixes and the ability to open larger databases.

 

[Gary Sutherland]

I'm running version .5815 which claims to be SP2. Downloading and installing the referenced update didn't change this.

G.

 

[Joe Crescenzi]

I'm running version .5815 which claims to be SP2. Downloading and installing the referenced update didn't change this.

G.

7423 is SP2 with the security patch.

Technically, Microsoft Service Packs were their way to distribute a combination of fixes and enhanced or changed features, but patches are just fixes.

 

[EinTerraner]

I've dloaded this on 07/17/2024

and the funny ununderstandable thing is the CreateDate is the 14.th, but the last update shows the 11.th
Those 4 OCX i do use in my projects

here the content of one of those files

 

[Chriss Miller]

The Bereznikers

You have the lat4est version SP2 plus Hotfixes.
SP2 would bring you back to 9.00.00.5815

I mean you could download and check for yourself, which version number the properties of the VFP9.exe file has. It's not only about the file version of the EXE, the runtime DLLs you have should match in their version and the gdiplus.dll should be from the security fix this DLL had.

Confirmed. The only thing that changed is the date of the web listing.

Good, the download link for SP2 from Bereznikers blog post does not work anymore. The little "wonder" is that MS even provides this SP2, still. VFP is a completely deprecated product, there are not even security fixes anymore. The downloads for SP2 and Hotfixes have beei moved to VFPX, this made this completely independent from any MS support: https://github.com/VFPX/VFP9SP2Hotfix3/tree/master