Remedy: First create the corresponding target directory with the Explorer, and then simply type in the path in the installer.īut the installer doesn't install all the essentials for VFP9. (In my case I install to \Develop\).īut that MS installer is somewhat stupid: You can't visually select a new directory when installing, the installer dialog remains empty. To install in "c:\Program Files\" folder should be awarded with the "Bozo of the year" for various reasons (development systems are not pure "only executable" end user programs), so you should install them outside of this especially monitored and restrictive folder branch. Attention: do not execute the SETUP.exe directly, but the VFPSTART.HTA.Īfter entering the key (which, by the way, is the same all over the world), you come to the path selection.
So you start normally with inserting the CD or an ISO image. Starting with Windows 7 we are confronted with two problems, which are not VFP specific, but sloppiness of the used installer. Beside this "simply copying over" for Lazy Joe ) of course a clean new installation should also be possible. VFP3 doesn't run without tricks on today's computers anymore, because we all have too much RAM (VFP3 can handle max 512MB RAM by default, SP1 had extended it to 738MB for that time an impossible value!) A possible Way out in Win7: Run in virtual XP mode, because this VirtualPC is configured to 256MB by default.īut back to the topic. (Attention: the /RegServer does not do this until VFP6, in VFP5 it was still "-R"). In the main directory there's a batch, which executes this /Regserver in the correct order (older versions first), so that always the latest version is registered as the last one. I have installed all FoxPro versions (starting from FoxBase+ over FoxPro1, 2, 2.6 for DOS and all Windows versions) parallel and executable in a folder D:\Develop\. For VFP9 this would be the VFP9SP2RT.EXE and then the XML2 stack as well as ODBC and OLEDB are now available.īy the way: I do this "copying over" several times a year, because I often set up a new disk, be it to test new Windows versions or to get a totally dirty computer up and running again. So: The easiest way to make any computer VFP compatible, is to use my runtime installer: At you can find the appropriate installers for all common VFP versions.
We'll get to them in a moment, but let's go one step after the other. are missing, which are no longer standard in the current Windows, but which VFP uses for the display of the TaskPane or IntellisenseManagers etc.
a DBF starts the VFP and displays the table in a browse.īy the way, there is another tool to clean up or reset VFP settings: DO HOME() + "VFPCLEAN.APP" checks the VFP internal mappings in the options dialog (paths to Genmenu, ReportEngines etc) and corrects them.ĭepending on already installed other programs it can be that such a copied VFP then already starts without complaint, mostly however then the MSXML2 libraries or the (at that time current, but in the meantime age-old) OCXe for Treeview, Listview etc. This option rewrites all file associations so that a double click on e.g.
The easiest way to do this is to click on "RUN (as Administrator)" in the "Right-Mouse-On-Windows-Start" menu then switch to the VFP directory and type in VFP9.EXE /REGSERVER and start it (If a message appears "Access to system registration denied", then it was without admin rights, and you can do it again). Here's the shortcut for those in a hurry: VFP can be moved from the old to the new computer in no time at all by simply copying the entire development folder from the old computer and then starting VFP with the addition "/REGSERVER" once with admin rights (!). I always hide all further language updates (mark all and then right mouse click), as well as the bad MS LIVE stuff.
In Win7 please have a look at the optional updates. Of course the setting should be set to "For Windows and other MS products" so that Office etc are also updated.
run the Windows update functionality until nothing more is reported.
Switching to Windows 10 is usually the typical reason.įirst, of course, Windows itself should be completely up2date, i.e. Since there have been a lot of requests about this in the forums lately, here is a list of all necessary steps to set up a VFP9 from 2004 on a virgin Windows of today. Update June 2021: New links added, because currently Microsoft broke every download link (This is the translation of my german blogpost from )