Well, Mr Dragan - I am glad you jumped into it - because another issue has popped up related to MSComCtlLib (SP6 OCX) and VFP 5.

Setting "AllowColumnReorder" to true allows the user to slide the columns around. It works great in VFP 6 (don't even need the ".OBJECT." mediary. But in VFP 5, it shares this little moment of joy:
AppName: vfp.exe AppVer: 5.0.0.402 ModName: mscomctl.ocx
ModVer: 6.1.97.82 Offset: 0000e4c5

Microsoft has a VB FIx here (for SP6 OCX):
http://www.microsoft.com/downloads/details.aspx?familyid=25437D98-51D0-41C1-BB14-64662F5F62FE&displaylang=en

The MS Caveat is:

Overview
This package updates two Microsoft Visual Basic 6.0 Common Controls:
mscomctl.ocx and comctl32.ocx to address the issues described in the KB
articles noted in the Related Resources section on this page.

This package will not install these Common Controls if they do not already
exist on the target system. <b><u>This package cannot be uninstalled</u></b>

.
The publish date for the "hot" fix is 4/27/2005.

QUESTION: Can (is it allowed) OCX SP6 implement with VFP 5? VFP 5 was shipped with OCX SP 5. OCX SP6 was not birthed until VS 6.

Should I use the SP5 OCX with VFP 5?

And - would the Hot fix (4.27/2005) for VB 6 (OCX SP6 MSComctlLib) apply to my VFP 5 project?

Any help appreciated - otherwise my demise will never wash from your hands.

Ya know - this is something Stewart (or ER) could help with - memories - memeories.

Thanks Dragan - if you get a chance to read the hot fix page - or know how I can determine what the publish date for my MSComctlLib is - it would be most helpful and perhaps delay my Hairi Kari.

I guess I should ask - is it okay to implent OCX 6 with VFP 5?

Remember - vote early and vote often!


>>I found the "issue"
>>
>>With VFP 6, and later, we could willey-nilley the OCX toolbar imagelist thusly:
>>
>>

>>with oTB
>>.imagelist=oImageListCtl
>>....
>>

>>
>>in VFP 5 - the engine likes the "object" specifier:
>>
>>

>>with oTB
>>.object.imagelist=oImageListCtl.object
>>....
>>

>>
>>And, "Yes", MSComctlLib (SP6) will work with VFP 5 under the previous provisos!
>>
>>And "yes", I missed you guys too
>
>Sorry for not jumping in with this, but yes - now that you solved it, I remember this too :).
>
>Man, it's been about seven years since I switched from 5 to 6. You expect anyone here to remember such a little thing, 4 versions ago, when computers were still using tubes? :)