Warning: Early Binding with Office

[JohnYingling]

Check out this MSDN link. For all those exporting data to Office, it appears that new versions of Office can break your code if you use early binding.

http://msdn.microsoft.com/library/default.asp?URL=/library/techart/VSOfficeDev.htm

Click on VB Frequently asked questions.
====================================================================
"If you are developing an Automation client for both Microsoft Access 97 and 2000, you should not use early binding: late binding is recommended. The Access 2000 object model was modified such that it breaks both binary (vtable) and dispid compatibility. Any client application that uses early or dispid binding to Access 97 might fail to work properly when run against Access 2000."
====================================================================

Below is what I use to get the benefits of IntelliSense without using early binding in production.
......

#If blnDesign then
    Dim objAppl as Word.Application ' Need reference to Type lib
    Dim objDoc  as word.document
#Else
    Dim objAppl as object 
    Dim objDoc  as object
#End if

You can set blnDesign in the Project Properties for the compile or define it in your code.
#Const blnDesign = True ' set to false when production compile

http://WWW.VBCompare.Com