Re: I have a VB project, but VC/COM question(s)

From:

"Igor Tandetnik" <itandetnik@mvps.org>

Newsgroups:

microsoft.public.vc.language

Date:

Sat, 29 Mar 2008 10:59:27 -0400

Message-ID:

<eFHi$1akIHA.5396@TK2MSFTNGP06.phx.gbl>

"Ralph" <nt_consulting64@yahoo.com> wrote in message
news:%23jcF%23VXkIHA.5820@TK2MSFTNGP04.phx.gbl

"Igor Tandetnik" <itandetnik@mvps.org> wrote in message
news:%23P66ZpDkIHA.4244@TK2MSFTNGP06.phx.gbl...

Alex Blekhman <tkfx.REMOVE@yahoo.com> wrote:

"SvenC" wrote:

You cannot do anything. The VC app developers must expose a COM
interface which is OLE automation compatible. Otherwise you
cannot
use it from VB.

IIRC, VB6 could use COM component directly without requiring
IDispatch

... but only if the interface is automation compatible (marked
[oleautomation] in the IDL).
--

Not true. VB can use either a 'normal' or 'vtable' interface

Yes, but only if this interface is marked [oleautomation] in the TLB,
and uses only automation-compatible types.

or an
'IDispatch' or automation interface.

You seem to believe that "automation" is a synonym for "based on
IDispatch". This is not the case. There exist interfaces not derived
from IDispatch that are nevertheless automation-compatible. Read the
documentation on [oleautomation] attribute.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925