Hi Mathias,

Thanks for the response, what version of VFP is your app running under?

Regards

Jon

>Jon,
>
>I will only answer 1 of your of your questions:
>
>I have been using that utility by Calvin for at least 12 months now on our of our apps running on 1000s of Windows based workstations from Win2000 to Vista. So far we've had not reported or known backward compatibilty issue. I must confess there are very few Win2000 systems in that sample.
>
>Regards
>
>
>>Hi All,
>>
>>I'm after a little clarification on getting one of my exe's to run on Vista. To start with my exe is named install.exe which is a bad start and therefore Vista prompts for authorisation.
>>
>>I have been looking at Calvin Hsia site, http://blogs.msdn.com/calvin_hsia/archive/2007/04/13/add-a-manifest-to-control-your-application-vista-uac-behavior.aspx, which describes adding the manifest into the exe and I have tried this on a VFP9 exe and it works brilliantly.
>>
>>What I need clarification on is:
>>
>>Does a VFP6 exe have a Manifest section in the same way as a VFP9 exe? From my investigation it seems that it doesn’t, but I may be wrong.
>>
>>Does the manifest actually need to be built into the exe, even in VFP6, as I have read in places that having the file in the same directory should be enough? But I can’t get this to work.
>>
>>I have read that adding the manifest to the exe could cause backward compatibility issues on XP, the dreaded blue screen, has anybody encountered this problem? I believe it’s been fixed but my concern is not all of my existing clients will have the patch.
>>
>>I could just rename the exe but it will need a few changes and a decent amount of regression testing to ensure I haven’t broken anything else. Adding a manifest file seems to be the easier way and my preferred solution.
>>
>>Thanks
>>
>>Jon