1. Download Visual Foxpro 9

Visual FoxPro 9.0 SP2 provides the latest updates to Visual FoxPro 9.0, including fixes to customer reported issues. The bug fix list for SP2 can be viewed or downloaded from this page.

I’m sure many die-hard FoxPro developers are curious if Visual FoxPro 9.0 SP 2 will install and run on Windows 10. Well, I wanted to be one of the first to find out,.So, let’s find outFirst, I installed Windows 10 Preview (64 bit) in a BootCamp partition on my 15” MacBook Pro. (Don’t worry about this Mac stuff, it’s still just Windows running on live hardware, just like if it were a Dell or HP computer). That went very smoothly, and I did a full install, blowing away the Windows 8 playground I had been using that partition, instead of updating it from Windows 8 to Windows 10.Next, I gently inserted the Visual FoxPro 9 CD that I still have from circa 2004. First, it prompted me to install some “Prerequisites”, which it did with no problems. Next I moved on to the main VFP install, and I took all the defaults, then the CD spun around for a bit, and finally, it gave me a nice message screen stating “Setup is complete” and “There were no errors during setup.” Looking good so far!!Next, I downloaded and installed, and once again, got this nice little affirming message box:Finally, I “installed” the VFP 9 Hotfix 3 for SP2 (i.e.

Download Visual Foxpro 9

Copied the replacement files to the correct places per the instructions in the readme file in the zip download).We now have a promising Microsoft Visual FoxPro 9.0 entry in the fancy new Windows 10 Start menu:Yes, but does it actually run??Now, I finally get to find out if we can run the fully patched Microsoft Visual FoxPro 9.0 SP2 Version.7423 on Windows 10. So, I launch it from the Start menu, and quickly go the Help – About screen:One small issue with Task PaneIf you launch VFP 9 it will initially show the the Task Pane, but you will get a small error in the view area of the Task Pane window. (Don’t worry, I’ll show you how to fix this below.)Class definition MSXML2.DOMDOCUMENT.4.0 is not found.The issue is that Task Pane requires MSXML 4.0 Core Services. If it’s not already installed on your Windows 10 machine, you will get this error reported in the Task Pane app from the VFP IDE.However, this problem is easily fixed You need to download the MSXML 4.0 Core package from:Once, installed, now Task Pane will work properly:Now, let’s run some codeOkay, it says the right version number all, but we need run some FoxPro code to make sure this thing actually works So, I just downloaded the from, and ran Thor.app to put VFP 9 on Windows 10 to its first test.

Thor uses tons of well-architected FoxPro code to do it’s magic, along with some UI forms, and it makes use of our beloved FoxPro cursors, so I figured this would be a good test. I selected about 10 of my favorite VFPx tools from the Check For Updates form in Thor, and it nicely proceeded to download and install all the tools, and gave this confirming output for each one on the VFP desktop as it did its work:I think we’re good folks!Next, I ran a few of these tools, just to make sure they’d fire off, and they did.

I’m pretty certain at this point, that my business apps would work just fine here, if I took the time to finish out this developer setup.So, I haven’t done any real coding work in the IDE, and I probably won’t any time soon, but from my basic tests in this experiment, it sure appears to me that our old friend Visual FoxPro is ready to continue its legacy of being an awesome development tool, even on Windows 10, and hopefully on Windows 20 and Windows 30 as well.Finally, here’s a peak at the whole IDE running in Windows 10. You can see I docked some windows, and you can see the shading effect that Windows 10 adds around the individual windows.Post navigation. I tested on Windows 10 (WindowsTechnicalPreview-x64-EN-US) several my procedures that are using the old Visul FoxPro 6.0 run time, the procedures work well using the MS treectrl Olecontrol, an ole Zip Unzip ctrl, obviously, accessing big DBFs (more than 1000000 records), connecting with MSSQLs and with IBM DB2 (via ODBC), and so on.The only problem is using some API of the WININET.dll, sometimes my class lose the return data (from a Foxisapi server), I will investigate better in the future.I tested the procedures on Windows 10 running on a Virtual Machine and quickly (is not the best test). Update to Meiryo font.Hi All. I tried replacing the Meiryo font via the Code References tool withthe Yu Gothic UI font, but that fails to replace as the expression value turnsout to be illegal. I also tried changing the font character set to default by the samemethod, but that failed for the same reason.

I guess because Meiryo is notwithin Windows any more.Eventually I went in at data level and manually replaced all Meiryo UIfonts with Yu Gothic UI. In some cases, I had to change the font characterset to default (1), then via the object properties, change the character setback to Japanese (128).Being fairly pleased with myself after such great efforts, I installed thenew application on to a Windows 8 machine only to find the applicationfalls over. Reason -: Yu Gothic UI is not standard font in Windows 8 or 7.Moral of story, make sure your chosen font is backwards and forwardscompatible. Hi Matt,Thanks again for the early tip on Windows 10, also the extra bit above what OS returns. I have this little utility which (I’ve acquired from various tips and) works well for getting the OS, so I thought I’d pass it on as a return gesture.code.

Just call it as RealWinVersion. Or better:. oOS = createObject(“Empty”)?

Hi Thanks for the info. I have been running vfp9 on Windows 10 for about 3 weeks and may have just discovered a small problem.I use the “Lock” command to ensure a unique number is generated when starting a new record. The “Lock Command” works but the “Unlock” command issued at the end of the routine gives an error message.

Never had the problem before and some of my DebtControl system users have quite a large number of staff all using the “add” a number routine at the same time.I have just removed the “Unlock” command and it is business as usual.I have 10 Business systems developed in visual fox used by 100’s of users and I am much to old to learn a new development language so long live VFP9. Hi MattmI have just installed vfp9.0 (+sp2) +hotfix 3 (from vfpx) on release win 10. On initial execution when the taskpane open I received an error: cannot create class msxlm2.domdocument 4.0.in syswow64,msxml3 and msxml6 are present with dates 7/10/15msxml2 and msxml4 are not present.examining msxml3 and msxml6 in the object browser shows no domdocument40 class in either, however msxlm3 had domdocument26 and dodocument30.I installed msxml4.0 sp3 which has the appropriate class and the problem went away.My question – why did you not see the same problem, or is this a new “feature”thanks,Ted. Ted – I didn’t notice this initially because I do not use the Task Pane.

However, I did confirm your issue on my Windows 10 install, and it is easily fixed:To be clear, this doesn’t stop VFP from installing or working properly to develop or run apps. The Task Pane requires MSXML 4.0 Core Services. You need to download itSo, download the MSI from that link (msxml.msi) and install it, then you’ll be running again!Thanks for bringing this up, and I’ve update the blog post to mention this issue, and report the fix.Happy FoxPro!!(Credit to Craig Berntson for answering this question on the following post:). One issue I’ve come across in Win10 is related to the Zoom setting in Display Settings. (The setting that says “Change the size of text, apps and other items”.If you change the zoom to greater than 100%, text seems to display fine on VFP forms but using VFP reports is an issue. The fonts are scaled up in the VFP report but the page size stays the same, resulting in the report not fitting on the page.

You will see the text truncated in preview.Has anyone seen this and had success in managing it? Yes, I’ve come across this issue and a thorough scouring of the internet has turned up nothing but your post above. Wondering how this could be, I took a guess that ReportBehavior is not a popular item among FoxPro programmers.

I have it set to 90 but must set it back to 80 to write ASCII files and PDFs using Amyuni. Now I’ve discovered that setting it to 90 results in the behavior you described but 80 will display the previews properly again. I may just resort to 80 and forget about it.

80 prints faster anyway and I have no other reason to use 90.Basically, the issue is caused by Windows 10 scaling fonts and forms automatically. On a high DPI monitor running Windows 10, like a Surface Pro screen for instance, the screen resolution is set to 200% so applications are legible but Fox programs think that it is 100% so the printing overwrites the right and bottom margin.Hope this helps although you may have discovered this already. I only found your post last night. Hi John,I am having this problem.

I bought a new Win10 Lenovo laptop with the his-res display (2560 1440). I am using RDP to log onto a remote server for my client’s. I connected an external 1600 x 12000 monitor and I can get the remote server Desktop to look normal, but when I Preview a report I get that problem your described. It also has the same issue when I run and Preview locally on the laptop without using RDP. The application is written in VFP 8. You mentioned “setting it to 80” and it works.

Since I’m using VFP 8, there is no SET REPORTBEHAVIOR command. Any ideas on how I can fxi this? It’s a major issue. Hello,I guess many of you guys has still running very interesting apps with vfp9 sp2I´d say the complexity of your (still today 2015) running applications and the good performance of vfp9 must keep you there.

Happens to me too.I am wondering what plans do you have?Are you staying in vfp9 for how long more?and if not, Which is the best platform to migrate?I have a few apps on production level doing just fine.these particular customers just don’t want to face the dilemma until its too late.I warned them and they know.I believe its too late already but then again investment is needed.So it would be interesting to learn about your plans if you may shareRegards. Our small data processing business (mailing list segments and prep), USPS Cass+NCOA services, etc, has been using Visual FoxPro9 and its predecessors all the way back to Ashton-Tate’s dBaseII in 1982-1983. We could not operate without it.We are preparing to replace our two server computers (a rackmount Dell PowerEdge/600 which we have used for self-hosting our website, equipped with Windows 2003 Enterprise Edition; and another machine equipped with Windows 2003 R2 Professional Edition).Our new system will be include a small Dell PowerEdge server suitable for rack mounting or sitting flat on a desk. We will also have two workstations. One will be the old chassis and drives from the Windows 2003 R2 Professional Edition computer, but with the operating system upgraded by Windows 10 Enterprise Edition, set up in 32-bit mode so we can run all our old 32-bit software programs. The other machine will be a similarly-equipped new Windows 10 Enterprise Edition unit, but in 64-bit mode.

Both these Windows 10 machines will be used strictly for database processing and CASS+NCOA job runs. In the future, we will alternately upgrade these two work stations with MS Windows Enterprise upgrades, starting with the old 32-bit machine.Questions:1) What are the file size limitations for VFP9 in Windows 10 Enterprise 64-bit, compared with Windows 10 Enterprise 32-bit?2) We have the VFP8 and VFP9 diskettes which our consultant had available from a Microsoft MSDN subscription, and which the consultant used for the original build in 2004. Will these still work now in 2016 for the build we will need for the new 64-bit work station? And can we assume that the Microsoft 32-bit upgrade to Windows 10 leave our VFP system extant?Thanks for any helpful advice.Arnold HarrisFast-Track Listmail608-798-4833. Matt, I am sorry I do not know you. What a wealth of information! I’ve been developing in FoxPro since 2.6.

So many times I have thought my company growth had exceeded VFP capabilities and tomorrow would be the end for my 20 year old FoxPro app. When oplock issues arose with Windows 7 and Server 2008, my app came to an unusable crawl. I thought it was the end. We are now running on Surface tablets and Windows 10. I am amazed everyday.

So many have helped me along the way. Thank You and the entire FoxPro community for all you do. I just upgraded from Win 7 to Win 10.

ODBC support for FoxPro has disappeared. I’ve sat through many support calls at Microsoft. Most support people had never heard of FoxPro and assumed it was some “3rd party product”.

As best as I can tell, there is no further ODBC support for FoxPro. I’m wondering when FoxPro will simply stop working on Windows 10 after some automatic update. No one at Microsoft could offer me any assurance that this will not happen. Technically, Microsoft stopped supporting FoxPro January 2015. Thank you for your reply, Admin That’s not quite the issue I’ve run into. I’ve also got MySQL ODBC drivers working just fine.I have a Word document that merged against a FoxPro table through ODBC.

That document no longer connects – not in Word 2007 nor Word 2016. The FoxPro ODBC driver disappeared from my data sources after the upgrade. I’m unable to install an ODBC driver for FoxPro.

Various Microsoft web links that are supposed to guide me to a FoxPro ODBC driver are dead links. Maybe someone else has run into this and found a solution?Now technically I cobbled together a work-around.

I export my DBF to XLS and reset the Word doc to merge against that and got through it. I only mention this dropping of support for the FoxPro ODBC driver as perhaps an early indication of what is to come. I don’t think we’ll get a warning.

Ever since upgrading workstations to Windows 10, we have been having a lot of problems with our FoxPro apps.1) Every time we rebuild the executable, the users get access denied when trying to run the program. Rebooting the workstation fixes it.2) Random record caching problems have started to occur. You update the record on one workstation, and another workstation does not see the update. You run a query and it bring in records that don’t match the selection criteria.

Weird stuff like this. It’s rare, doesn’t happen often, and because of that is very difficult to duplicate.This did NOT happen with windows 7 or XP workstations. These applications have been in place for years and are rock solid. Only the users on Windows 10 workstations are having these problems.

Still trying to get InstallShield Express to run a complied VFP 9 on either W7 or W10 machine. My program looks for missing or corrupted data files first and opens a form for backup restore, but the machine just flashes the title of the form a few times and closes, despite the fact that I have included all files. Tried some path tricks, no luck. The program works fine if I delete a file on the W7 machines that have full VFP9 installed, and runs normally with all files present.

I really would like to be able to distribute this program with InstallShield. I’m not a pro, but a pretty good debugger, this has me stumped. Any suggestions are welcome. I have a legacy VFP web app where I rely on a VFP automation server to debug locally.

It works by simply doing this:oVfp = CREATEOBJECT(“VisualFoxPro.Application.9”)oVfp.visible=.T.This has worked on every version of windows except for Win 10. The visible=.T. Does not make VFP visible.This works just fine:oXl = CREATEOBJECT(“excel.application”)oXl.visible=.T.I can reproduce this behavior through the VFP command window. I am wondering if there is a compatibility setting that could possibly make VFP show itself or if there is something with my specific install. I’ve tried many things with no luck.Thanks,Chris.