Hi Rick,

>Alex,
>
>I've tried that but it doesn't work for the Common Control OCX as far as I can tell. At least not in runtime applications.
>
>I wonder what exactly needs to go into the manifest file especially in this section:
>
>

><assemblyIdentity
>    version="7.0.0.0"
>    processorArchitecture="X86"
>    name="Microsoft.VisualFoxPro"
>    type="win32"
>/>
>

>
>What would you put there for a custom application? I'm guessing that for Win32 apps, it doesn't matter.

Generally, yes, it doesn't matter, you may put there a manifest version, the name of your company, product and application, etc. only "processorArchitecture" and "type" attributes depending on the type of processor architecture and type of application, but you may put "*" there for all types.

>IAC, it doesn't work for the MSCOMCTL.OCX file...

>+++ Rick ---
>

Yes, you're right the manifest file doesn't work for the MSCOMCTL.OCX. That looks so funny all controls still use old comctl32.dll instead of new one even if you place a manifest... I think no one API function helps; we need to wait for the updated OCX files if they will be available some time, of course...

So, use my controls (they support WinXP visual styles) and enjoy :-)