Thanks Tore. This is the problem (sorry - edited). The problem occurs if the word "update" appears in the exeutable name, file description or program name under version info.

>See Message ID: 1472315.
>
>>That is quite incredible - my project is called "quick_update". If I compile it as any random name it works and Windows 7 does not add the UAC shield. If I compile it as quick_update.exe then it gets the UAC shield. Very weird. ...
>>
>>Thanks !
>>
>>
>>
>>
>>
>>>Have you tried to rename the executable? A project of mine gets marked if I call the resulting executable updater.exe, but comes out perfectly if I call it wbd.exe.
>>>
>>>>The projects and the exe files I am compiling them to are all on my local hard disk (partition D).
>>>>
>>>>None have OLEPUBLIC.
>>>>
>>>>I had 6 VFP8 projects that this happened to. For 5 of them I changed the version info to some other values; I changed the File Description and Product Name fields to something else and then re-compiled and Windows 7 then did not add the UAC shield to the resulting exe anymore! For the last project nothing I do makes a difference. Debug on/off, encrypt on/off, add random files, remove files, change version properties, nothing. As soon as VFP8 finishes compiling the exe Windows 7 adds the UAC shield to the icon.
>>>>
>>>>
>>>>>Are they located on a local or network drive? Do they include COM classes (OLEPUBLIC)?
>>>>>
>>>>>>No, not really. I am asking a different question. I have 2 projects. They are virtualy the same. Compile one and I get a normal exe with no UAC shield and it runs normally. Compile the other and imeediately Windows 7 adds the UAC shield to it before I even try to run it i.e. directly at compile completion.
>>>>>>
>>>>>>I have found that messing around with the Version fields (from the compile dialog), company name, trademarks, etc, seems to remove the sheild and hence the UAC requirement ???
>>>>>>
>>>>>>But cannot remove it from one other exe no matter how I mess around with the version info.