[AccessD] Missing references

<<<
each property/method reference must make a call
to lookup the functions address.  
>>>
Yes, Jim, that's how VBA works internally for late binding.

--
Shamil
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Dettman
Sent: Tuesday, February 20, 2007 6:11 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Missing references

Shamil,

<<When an object is created in memory, COM returns a pointer to its IUnknown
interface, whose QueryInterface() function VB then uses to locate a given
interface. All objects include the IUnknown interface, while only objects
capable of late-binding support the IDispatch interface. >>

  Thanks for that site.  I tried hunting for a bit yesterday to find
something that specifically stated that when you create an object with a SET
statement, the only thing that happens is that you get a pointer to the COM
object.  The above statement from the site you pointed out states exactly
that.

  It's as I remembered it; each property/method reference must make a call
to lookup the functions address.  Those may be cached somewhere, but the
calls are made each and every time.

Jim.