The package dates is April 2005. And it makes a big BIG big difference. I want to say the images look "themie" - even in non VFP desktop services.

But the stability is what most impressed me. Until April 2004, a VFP 5 project could not use eith SP 5 or SP 6. Iinstalled - ran a test on the VFP 5 project - and a major "leak" issue was wiped away.

I looked at my VFP 6 and 8 projects - and the images had "shadows" (wit MSCOMCTL SP-6!!!) just like other windows apps had.

A you know what - a couple of us were banging on the door when Levey or Stewart were hanging here - and no one told us abot this update (memory leak fix) was available.

I have spent of lot of time mapping work arounds so my projects could use OCX. The really strange thing is that they work (after some effort) with VFP 6 and later - but they crashed on specific methods [always] in VFP 5. I installed - and my VFP 5 SP 6 MSCOMCTLLIB conreols fired without a flicker.

It seems tha the Fox Team was addressing the OCX leaks from inside VFP - that's the only explanation I can come up with to explain why they failed in VFP 5 but worked (after some "work arounds") in later versions. And the real pain is that many of us who used VFP 5 and tried to get the OCX to work gave up - avoided them through later versions.

I think I can remove a bunch of work arounds from my library. Download em - you see immediately what I mean.

The biggest little secret ever - I had to fig and dig and dig - and was about t pop a grid on a form when I found that that advertized a VB6 OCX upgrade - none of the links included a notice for VFP developers (Why am I not suprised!)

Get the word out - the update is probably one of the most significant events in my history with VFP. ANd no one - even the insiders that came to this board and heard our wails - ever told us.

>What are the file version dates and version number for the ones you installed with the download? I have on my system (with VFP 9SP01 installed) the following:
>
>COMCTL32.OCX dated 11Oct99 v6.00.8105
>
>MSCOMCTL.OCX dated 23Feb04 v6.01.9782
>
>These were determined by going to the SYSTEM32 directory and right-clicking of the files and selecting "Properties".