> Thanks for the links.
>
[quoted text clipped - 9 lines]
>
> Is there any online help explaining Resource files?
Regarding this thread.... I attempted to create an
applicationname.exe.manifest file and placed it within my VB6 project
directory. I noticed that even though I was not calling the
InitCommonControl routines... when I compiled my VB6 applicatin to EXE, it
would return an "Out of Memory" or "Object or With Statement used..." within
my main routine in my module.
Running the applicaton within Debug mode in IDE worked fine.
I then renamed the manifeset filename to .bak and recompiled... and all
worked fine again.
I guess the COMCTL32.DLL V6 still looks for manifest files whether I call
functions or not???
Also, I tried added the InitCommonControl within my forms initialize routine
and recompiled... I did not see any XP-style theme when I launched the
application. Now I did not change the manifest file from the default... so
all old application names, etc., is the same. Anyone have any ideas why the
call appeared to work but nothing was noticable on screen?
>> Thanks for the links.
>>
[quoted text clipped - 48 lines]
> Kingston upon Thames
> UK
Peter Young - 30 Nov 2004 04:02 GMT
> Also, I tried added the InitCommonControl within my forms initialize routine
> and recompiled... I did not see any XP-style theme when I launched the
> application. Now I did not change the manifest file from the default... so
> all old application names, etc., is the same. Anyone have any ideas why the
> call appeared to work but nothing was noticable on screen?
All you need is the manifest (either as an external file or an embedded resource) and the call to InitCommonControls.
Are you running it on XP?
DavidM - 30 Nov 2004 14:57 GMT
Yes --
>> Also, I tried added the InitCommonControl within my forms initialize
>> routine
[quoted text clipped - 8 lines]
> resource) and the call to InitCommonControls.
> Are you running it on XP?
Peter Young - 30 Nov 2004 18:00 GMT
> >> Also, I tried added the InitCommonControl within my forms initialize
> >> routine
[quoted text clipped - 9 lines]
> > Are you running it on XP?
> Yes --
Both vbAccelerator.com and vbAdvance.com provide VB projects that demonstrate how to do this. Do those render correctly
for you?
Randy Birch - 30 Nov 2004 23:47 GMT
Under XP, if there is a manifest with the same name as the exe, Windows
attempts to use it. If the application does not call InitCommonControls, and
does not have any VB5 common controls on the form (which also call
InitCommonControls), the exe will fail in any number of manners, none
pretty. Comctl32.dll has nothing to do with the use of the manifest -- it is
provided to inform Windows that Windows should use the Version 6 features of
the common control dll.
And to see the XP-styled 'themes' applied to the common controls, you must
be using the VB5 controls, not the VB6 ones. The VB5 controls use
comctl32.dll; the VB6 ones do not.
Finally, successfully applying the themes with InitCommonControls and a
manifest will not result in forms taking on a themed appearance, as with
Office 2003 under XP. That requires additional magic far exceeding a simple
api call.

Signature
Randy Birch
MS MVP Visual Basic
http://vbnet.mvps.org/
: Regarding this thread.... I attempted to create an
: applicationname.exe.manifest file and placed it within my VB6 project
[quoted text clipped - 69 lines]
: > Kingston upon Thames
: > UK