![]() |
|
#1
|
||||
|
||||
![]() Hi tinfanide, This issue is that, when using late binding, the calling app has no access to the called app's object model until the code is compiled. In this case, Excel has no way of knowing what wdBorderTop or wdLineStyleSingle, for example, are. FWIW, if you'd prefer to leave the parameters unchanged, you could declare them beforehand with code like: Const wdBorderTop As Long = -1 Const wdLineStyleSingle As Long = 1 This has the advantage that expressions like: .Borders(wdBorderTop).LineStyle = wdLineStyleSingle are much easier to interpret than: .Borders(-1).LineStyle = 1
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#2
|
|||
|
|||
![]() Quote:
|
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
![]() |
tinfanide | Excel Programming | 7 | 12-12-2011 05:21 AM |
Problem: object library invalid or contains references to object definitions | aligahk06 | Office | 0 | 08-19-2010 12:29 PM |
Using Office Premium 2007 Trial with Already Installed Office Home and Student 2007 | SME | Office | 1 | 10-07-2009 06:51 AM |
![]() |
OfficeDude | Office | 3 | 08-16-2009 02:11 PM |
Access Object library 10 | Gyto | Office | 0 | 10-09-2008 09:04 AM |