I have an ActiveX control that I developed with ATL that I recently enhanced. I updated the type library version from 1.6 to 1.7.

The new control works fine with Visual Basic and Internet Explorer. However when I try to load it into Excel I get the message "Cannot insert object".

I assumed the problem was a mismatch between the version of the type library and a version specified in the header for the control. However synchronizing them did not help.

Someone on the vc.atl board suggested that Excel might be caching the old type library. How can I check this? Does anyone have any other ideas what might be causing this problem?

Nothing in the KB on the lastest version, but for Office 97, there were some
restrictions.

http://support.microsoft.com/default...&Product=ofw97
XL97: Error Inserting ActiveX Object in a Worksheet

http://support.microsoft.com/default...&Product=ofw97
OFF: .Exd Files Are Created When You Insert Controls


another possibility:

http://support.microsoft.com/default...80&Product=ofd
PRB: Error Message "Cannot insert object" in Excel

--
Regards,
Tom Ogilvy


"DogMan" wrote in message
...
I have an ActiveX control that I developed with ATL that I recently
enhanced. I updated the type library version from 1.6 to 1.7.

The new control works fine with Visual Basic and Internet Explorer.
However when I try to load it into Excel I get the message "Cannot insert
object".

I assumed the problem was a mismatch between the version of the type
library and a version specified in the header for the control. However
synchronizing them did not help.

Someone on the vc.atl board suggested that Excel might be caching the old
type library. How can I check this? Does anyone have any other ideas what
might be causing this problem?

Thanks for the suggestions, Tom. Unfortunately none of the 3 suggestions applied.

I have been working on this problem with the assumption that it has something to do with your 3rd suggestion, but it seems to be something else.

"Tom Ogilvy" wrote:

Nothing in the KB on the lastest version, but for Office 97, there were some
restrictions.

http://support.microsoft.com/default...&Product=ofw97
XL97: Error Inserting ActiveX Object in a Worksheet

http://support.microsoft.com/default...&Product=ofw97
OFF: .Exd Files Are Created When You Insert Controls


another possibility:

http://support.microsoft.com/default...80&Product=ofd
PRB: Error Message "Cannot insert object" in Excel

--
Regards,
Tom Ogilvy


"DogMan" wrote in message
...
I have an ActiveX control that I developed with ATL that I recently
enhanced. I updated the type library version from 1.6 to 1.7.

The new control works fine with Visual Basic and Internet Explorer.
However when I try to load it into Excel I get the message "Cannot insert
object".

I assumed the problem was a mismatch between the version of the type
library and a version specified in the header for the control. However
synchronizing them did not help.

Someone on the vc.atl board suggested that Excel might be caching the old
type library. How can I check this? Does anyone have any other ideas what
might be causing this problem?

Hi

First of all, I would like to confirm my understanding of your issue.
From your description, I understand that you have an ATL control of version
1.6 which works fine when you insert it into the Excel worksheet.
Afterwards, you make some changes to the control and change the version to
1.7, the you will get the error message "Cannot insert object".

Have I fully understood you? If there is anything I misunderstood, please
feel free to let me know.

Have you changed the progid or GUID, when you change the version?
To isolate the problem, you may try to insert the original version to see
if the problem occurred.
Try to recreate a new ATL object and use a new progid and GUID with the
changed version's code, did the problem persists?

You may have a try and let me know the result.
Also can you make a simple reproduce sample and send to me by removing the
"online" from my email address?

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.