[AccessD] Dealing with References across versions

Late binding simply means that when you open an Outlook Object (or any other Automation Object) your object variable is:

Dim objOtl as Object

Instead of Early Binding:
Dim otlApp as Outlook.Application

If you use early binding during development you gain the advantage of intellisense in working with the object model, then you can change it to late binding by re-dimming the objects and clearing the reference to Outlook.

THere's the brief version.

-Chris Mackin



-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Arthur Fuller
Sent: Thursday, December 30, 2004 8:52 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Dealing with References across versions


I wasn't sure how else to title this. I know that it's been dealt with 
in the past, but I can't remember under which topic.

Here's the issue. I develop the app under Office 2002. Some users run 
Office 2000, some 2002 and one 2003. I make use of both Outlook and Word 
in various parts of the app. Then on various machines I get busted 
because the reference is to Outlook 10 and they're running 9, etc.

I seem to recall that there is a "late binding" solution to this, but 
that's all I remember.

TIA,
Arthur

>  
>


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.298 / Virus Database: 265.6.6 - Release Date: 12/28/2004

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com