>>>>>>>Also, what happens if I installed SP2 over SP1?
>>>>>>
>>>>>>It will not work
>>>>>
>>>>>Not entirely true. It'll work if xBase components of VFP9 SP1 hasn't been modified. Any modified components will not be updated to SP2.
>>>>
>>>>Now I'm puzzled. What does "xBase components of VFP9 SP1 hasn't been modified" mean. What component. Just out of curiosity - it wasn't that hard to reinstall.
>>>
>>>The "xBase components" are VFP components that are written in VFP, like FFC, Wizards, etc.
>>
>>You mean if one alter them? Do you mean somebody alters them in the place where they are installed? What a cruel idea ..
>>
>
>:-)
>
>>Things that should be no problem if one is working under "User" account ...
>>
>
>Actually the Vfp IDE itself is cruel enough to (try to) update files in Home() and its sub-folders.
>If you are using/testing Vista/Win7, you can see them in the "C:\Users\Agnes\AppData\Local\VirtualStore\Program Files\Microsoft Visual FoxPro 9\" folder after a while.
>Mine for instance contains vfp9err.log, genmenu.fxp, foxtask.dbf/fpt, foxcode.dbf/fpt, browser.dbf/fpt, and many others.
>
>
>Regards
>-Stefan

Design flaw. Example how long VFP was not included in the general progress of M$ OS. (I've started with 5.0 and it was not up to date)
Looks like the builders need to be moved to a directory usable for each user on the comp. Or you can rewrite the builders so that they store there stuff to something meaningfull like %ALLUSERSPROFILE%\Microsoft\VFP9\... . If you do post it to http://vfpx.codeplex.com/

But this would be a change to the XBASE components ...

Agnes