Susan Harkins
ssharkins at bellsouth.net
Mon Jul 12 13:50:20 CDT 2004
I kind of see the terms early and late -- in Access -- a bit differently than the way most documentation wants to define them. To me, early just means the library is referenced, hence the objects are instantiated, but not being used -- late, the object is instantiated at the time it's needed -- the reference is implicit. I see a lot of documentation that refer to setting references manually via the References dialog box as "early" binding, but using the References collection and object are never mentioned -- however... Seems to me you're setting the reference and instantiating the objects without using them, so, to my mind, it's early. Susan H. I certainly would call what I did in this respect early binding. Charlotte Foust -----Original Message----- From: Susan Harkins [mailto:ssharkins at bellsouth.net] Sent: Monday, July 12, 2004 9:17 AM To: 'Access Developers discussion and problem solving' Subject: [AccessD] more on early versus late binding This is a question of just terminology. I understand the difference between early and late binding, so nobody needs to launch into an exhaustive explanation. :) My question takes us back to the VBA's buggy References collection and Reference object. I'm assuming that if you decided to use the available properties and methods to set references this way, you'd consider it early binding. Anyone disagree? Susan H. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com