>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.

Hold your horses, and that hairy curry. There's no way to know the date and version for mscomctl... I know I once had three different files with the same version number, but their lengths, create and update dates were completely unrelated and out of whack as well. Took me several reboots to find the proper one ;).

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

Now with my flaky memory, I seem to remember that at that time I had both OCX 5 and OCX 6 installed at the same time, and I think that the only crash combination was to use OCX v6 with VFP v6; any other seems to have worked. The bad news is that I wasn't really sure which one was I using and when :).

Before you try any MataHari, maybe you could just build the app, install it somewhere and give it a try?

Also, I figure the OleControl may use the generic (i.e. not version-specific) name of the OLEClass, in which case it will use whatever's on the current machine, and your setup may (or actually should) refuse to reinstall the OCX, because it's a part of the OS. Or it may reinstall the OCX, but not the underlying dlls.

OK, just checked: any proper installer should not try to replace the dlls, but you may try with the OCXes. OCXes being more or less a COM wrapper around the dlls, I figure you should just use the newer. They wouldn't have made v6 if v5 was that good :).