Thanks NickHK

The control registers easily using Regsvr32 and only needs oieng400.dll
and imgcmn.dll to be in \system32\. It shouldn't give any trouble in
2002.

One possible clue I found relates to its version number in the
registry, see http://support.microsoft.com/kb/q171280/. The Win2k OCX
registers in the registry as ver 2.2 which would be about right (the
latest Pro version is ver 2.8), but if you rightclick the OCX, under
properties it is ver 5.00, and in code ImgEdit1.GetVersion returns
"5.00.2195.6601", which would also be about right for the "lite"
bundled version.

I've tried tweaking the version numbers in the registry but not found a
combination to fix it for 2003. I can send you some code to make it
run in XL2002 with intellisense, if that would help.

I'm mighty grateful for your help - thanks again.

NickHK wrote:

I can use this control in VB6, so design time licensing is OK.
Still no joy in XL2002 though.

NickHK

"Marcusmaximus" wrote in message
ups.com...
Kodak's old ImgEdit.ocx has worked for me with every 32bit version of
Win32 and Excel up to 2002. But opening an XL2002 workbook (with an
ImgEdit control embedded on a sheet) in XL2003 fails: although the last
saved image displays, the control is no longer there as an embedded
OLEObject, and isn't recognised by vba.

It's there in the XL2003 Tools/Refererences of course, and it's icon
even appears in the sheet toolbox. But trying to drop ImgEdit onto a
2003 sheet returns a "Cannot insert object" error, while trying to drop
it onto a form returns "The subject is not trusted for the specified
action" error.

It 'feels' like the previously satisfactory ImgEdit registry entries
don't work for XL2003. Any ideas, anyone?