Some of the C++ COM server dual interface routines are not detected by Excel.

Question

4.00/5 (1 vote)

See more:

I have an MFC MDI application with the automation layer implemented as dual interface. So the the early and late binding clients are supported.
With the early binding clients as C#, etc. everything is fine, but late binding clients in this case the Excel, VBA report the "Run-time error '438'. Object doesn't this property or method.".
Looks like the late binding clients do not see some of the methods from COM interface.
Does enybody encountered this kind of problem?
And what could be the resolution.
Any kind of suggestions appreciated.
Thanks.

Posted 4-Jan-13 4:11am

oleg63

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Maxim Kartavenkov · Answer 1 · 2013-01-10T01:19:00

Solution 1

Hello,

It looks like you have typelibrary linked or objects idl with different version of
the app than actual ocx.
Does your issue happend due calling some methods?

Some useful information I think you can find here:http://www.vbforums.com/showthread.php?460591-RESOLVED-Runtime-error-438-Object-doesn-t-support-this-property-or-method[^]

Regards,
Maxim.

Posted 10-Jan-13 1:19am

Maxim Kartavenkov

Comments

oleg63 10-Jan-13 11:58am

Thanks Max,

Yes, some methods are affected, some are not during the Excel VBA calls.
The same routines doesn't work if I call them from MATLAB.
Interestingly the MATLAB can see the all COM interface methods, but when I try to call problematc ones, it reports - "Error: method or property not found".

Maxim Kartavenkov 10-Jan-13 12:41pm

You also can try retrieve methods at runtime from IDispatch and invoke them directly without binding.

oleg63 10-Jan-13 13:16pm

But everything must work from Excel as well.
Now I'm checking on proper TLB embedment inside the executable.

Maxim Kartavenkov 10-Jan-13 13:26pm

try to look at that posts: maybe you will find some useful things: http://www.google.ru/search?hl=en&q=Run-time+error+%27438%27

Rob Grainger · Answer 2 · 2013-01-11T11:06:00

Solution 2

Maybe you've something in the methods that are failing that is not automation-compatible.

If you post the declaration of the failing method (IDL/C++) then it maybe possible to identify what.

The following subject lists Automation Compatible Types[^]

Posted 11-Jan-13 11:06am

Rob Grainger

Comments

oleg63 11-Jan-13 17:17pm

Thanks Rob,
But I use only automatin types. It was verified on first place.
I have a very heavy project, now I'm stripping down it to purely MFC MDI project.
Just making sure another application stuff is not affecting the COM interface.