My quest for Windows 7 manifest file for a VB6 exe

So, I am currently running a common problem trying to deploy a Vb6 application written and developed for Windows 2000/XP into the Vista/Win2008/Windows 7 world.

Problems
#1 - User Access Control - I get prompted by Windows about I do not know anything about this program are you sure you want to allow this.

#2 - Run as Administrator requirement:  Under compatibility for the Application short-cut, enabling run as Admin.  Turns out my project is creating and storing session and user in Program Files\App Folder\ in sub folders.  Which is being discouraged by Microsoft in Windows 7.

Possible Solutions:
#1 - On workstation after deployment, Run application with Run as Adminstrator turned on.
        This is an okay workaround but requires every workstation to be touched.
#2 - Use on a manifest file to set the execution permission to Administrator
        Alots and alots of discussions on the web and StackoverFlow.
        Found this gem Manifest creation tool - http://www.vbforums.com/showthread.php?t=606736
      
        Downloaded it.  I was able to create an apparently correct manifest file but  it did not work.
        Still trying to find out why.  
        Related post - http://stackoverflow.com/questions/4489165/vb6-manifest-not-working-on-windows-7/4496389#4496389

 My question if any wants to answer it and earn big big karma points....
What is the best solution to force a VB6 application to run as Administrator premissions
    - Is it really possible for VB6 and Windows 7?
    - Is the problem with session data in ..\Program Files\My App\  really the whole issue?
  
Any advice will be welcomed.  Email: gary.Kindel@gmail.com

Thanks

Installing webservice on WIn2008

Flexera Software - Knowledge Base: "Q200236: IIS support for Windows 2008 and Vista SP1

Reviewed installer script, worked

Needed Installshield2008 update to support Windows 2008


- Sent using Google Toolbar"

How do I get a verbose log? - Flexera Software Community

How do I get a verbose log? - Flexera Software Community: "You can create verbose logs for InstallScript MSI projects by launching the setup with the following command line:
setup.exe /verbose'C:\PathToLog\LogFile.log'

You can also enable the Windows Installer logging policy in the registry, however, the resulting output will be multiple log files instead of a single log, and some information from the script engine will not be logged.

- Sent using Google Toolbar"