Hi,

As I said previously all changes made should be available to app layer via virtualization, if not MS has a problem, report it as a bug, this was one of the things they said would be totally transparent.

>>Hi,
>> I was lead to believe that Vista would handle all the redirection for all calls to an entry that is virtualized.
>>
>> Can anyone from MS comment.
>
>
>If the application is setting registry values and retrieving the ones it set, it works OK under the VirtualStore key.
>
>I got burned because I used regedit to add/update keys under HKLM\Software\whereever which is what my application is trying to use, but the application doesn't see the actual HKLM\Software\whereever keys - it sees Vista's virtualized HKCU\SOFTWARE\CLASSES\VirtualStore\MACHINE\SOFTWARE\whereever which does not reflect the changes I made with regedit.
>
>I'm not sure if that is a compatibility issue with the registry vcx or just one of those Vista 'features'.
>
>>
>>>I've spent all morning trying to figure out why my VFP program kept getting wrong data from the registry.
>>>
>>>I set the data using Regedit under HKEY_Local_Machine\Software\myprogramname. The keys and values are there no problem.
>>>
>>>My application using the registry class tried to get the current values and kept coming up with values that were not what was there.
>>>
>>>Why?
>>>
>>>Because @#$%#$ Vista has a VIRTUAL copy of the registry for the application under HKEY_CURRENT_USER\SOFTWARE\CLASSES\VirtualStore\MACHINE\SOFTWARE\myprogramname that was set a few weeks ago by the program using the registry class to set HKEY_Local_Machine\Software\myprogramname.
>>>
>>>Can the registry class check the real HKEY_Local_Machine\Software\myprogramname like it does in the good MS operating systems? Apparently not.
>>>
>>>What a load of sh1t.
>>>
>>>I may sound pi$$ed off.
>>>
>>>I am.