We fully realize that the new ComCtl32 has the potential to break some applications.
To prevent this, ComCtl32 version 6 is installed as a shared assembly,
side-by-side with ComCtl32 version 5, which is installed in the System32 directory.
The new DLL is only available to applications that provide a manifest telling the
operating system that they work with the new DLL. If they do not provide a manifest,
existing applications continue to use ComCtl32 version 5.
Versions 5 and 6 both ship with Windows XP and are installed side-by-side.
We'll talk more about manifests in the next section.
....
To make sure that your application uses the new visual styles in Windows XP, you need to make sure to link to ComCtl32 and use a manifest to specify the dependency on ComCtl32 version 6.
If you have any owner-drawn controls, start asking the uxtheme.dll to draw them, rather than drawing them yourself.
You'll need to do this if you want them to feel like the rest of the UI.
....
Then, the problem is not within VFP, but it is external to it.
We do have to find/write a Manifest for VFP8.
Dorin Message #896440 demonstrates that it is possible
to use the controls with Themes in VFP7 and, the think, in VFP6 too.
Ok?