Basically .. whenever an app tries to write to "Program Files", Vista says no way and instead "copies" the file to the virtual store and then does the change over there. Vista then knows to run the "copy" sitting in the virtual store instead of the original.

The problem with FoxPro is this .. use the class browser to look at a class in the FFC directory. Don't change the class .. just look at it. Surprise ... FoxPro tried to WRITE to the file .. so Vista put a copy in the Virtual Store. From this point forward, the classes in the FFC are now in the Virtual Store. Now I come along and try to load a new version of FoxPro which goes ahead and installs the FFC files underneath Program Files like it's supposed to. But guess what .. the OLD files are still sitting in the Virtual Store. So now I go to run the FFC stuff .. and Vista grabs the OLD ones sitting in the Virtual Store because 3 months ago I happened to look at the class. I have to clear out those files in the virtual store manually.

PITA!!!!!!!!


>I haven't figured out that whole virtual store thing yet. I thought only applied to OS components.
>
>>I'm also a little leary of the Vista "Virtual Store" issue and whether I'll have to clear that out. I figured I would unintall VFP 9, look to see if the virtual store is still there, and if so, delete it. Then install SP2.
>>
>>However ... NEVER EVER load new software on your machine just before speaking at a conference!! < g > There's no way I'm going through that just days before I fly to Phoenix for Southwest Fox!!!!