The hotfixes are cumulative, you only need to apply the last one, their only prerequisite is VFP9 SP2 existing and then they come as an EXE that mainly is a self-extractor giving you some files and a readme.txt about what to do with them. See thread184-1796727 -
(MS doesn't provide the Gotfixes anymore, but VFPX is a good last home, Doug Hennig has this and GitHub is owned by MS, too, so this is as close as it gets to the official version. Just search a bit in this forum and you find all this.
Regarding problems due to UAC I think but I am not sure you also reported something within the IDE not to work as expected and the underlying reason for that on a low level can easily be UAC file redirection. Some tools and library parts of the IDE are actually written in VFP itself, that's why I, for example, talked about PRGs. When the FXP then is not generated in place but elsewhere that's not even the core problem, as that also happens in turn when reading or executing. Anyway, there are things that are quirky as VFP is acting within the Home folder when you make use of wizards, builders, tools like class browser and object browser, even just options, several system files, code references, etc. The way VFP coped with this before UAC as program files still also was write-protected (that's not new with UAX) is giving more permissions to the group of main computer users. With UAC not even admin users have this direct permission to write in Home. So you better give VFP a home outside such system folders.
C:\VFP9 3would be okay, yes. You'll also see when you later run VFP and then ? HOME() this will reflect your choice, as, well, this simply is the VFP Home() folder now.
Just don't install into the root C:\ drive itself. You'll notice whether a folder is problematic when you create it. For example, try to create your own folder within Program Files. You'll see what this asks of you so you'll also see when it doesn't that this folder location is unproblematic, in short, your question answers itself.
And as I said in the other thread or a few days earlier/later, the directory you specify is the Home folder, it's directly where VFP is installed, the installer does not create a "Microsoft Visual Foxpro 9" or similar there.
WOOdy, working with multiple VFP versions tells, he has a major C:\Foxpro folder with subfolders for each version, as that principle, always works the best. For security reasons, you might pick C:\Foxpro\VFP9 and then only give yourself, your own account permissions in C:\Foxpro\ which are inherited for every subfolder within. Or only give that to Administrator and create a shortcut to VFP9 that run it as Admin (you find this run-as possibility generally as a property of the shortcut, nothing only specific to VFP), which has the added benefit every project containing OLE public classes will not throw a warning with builds and automatically register for you. (You'll still need a setup that does that for end users/customers.
Bye, Olaf.
Olaf Doschke Software Engineering
