Application"), etc, but I hate to give up strong typing, etc.Can anyone suggest a superior way to handle this issue of backwards compatibility with older versions of MS Office?If you are looking to dig in to Identity 2.0, keep reading!Many of the customizations we previously needed to add on our own under Identity Version 1.0 have now been incorporated into the Version 2.0 RTM.If you ask me, I prefer Late Binding (where you don't create references and use Create Object to create an instance) An interesting read.Topic: Using early binding and late binding in Automation Link: My Suggestion Don't give up Early Binding if you like it because of intellisense.This article has also been published on Microsoft Office Online: Working with Excel tables in Visual Basic for Applications (VBA) In Working with Tables in Excel 2013, 20 I promised to add a page about working with those tables in VBA too. On the VBA side there seems to be nothing new about Tables. Best regards, For a cell within an Excel 2007 Table (the table is named "Table1"), with banded coloring of cells within the table, the . Color Index property of the cell returns "No fill" regardless of the cell color. Color Index always returns -4142 for both Green and White cells colored by Table banding. Color Index -4142 Then '-4142 corresponds to No Fill.

The only disadvantage is the installation procedure, but I bet there are more positive aspects then negative when selecting Windows Service over applications running Windows Scheduler.If you want full control over your table style, you'd better duplicate a built-in style and modify and apply that style to your table. The code comments show you where Excel 2003 differs from 2013, 20. Let's start with finding all tables on the active worksheet: Sub Find All Tables On Sheet() Dim o Sh As Worksheet Dim o Lo As List Object Set o Sh = Active Sheet For Each o Lo In o Sh. Sub Selecting Part Of Table() Dim o Sh As Worksheet Set o Sh = Active Sheet '1: with the listobject With o Sh. If I have a spreadsheet where I've referenced MS Outlook 14.0 Object Library from the VBA editor, and a user who only has MS Outlook 12.0 installed, then when that user opens the spreadsheet, they get a compile error on this line: ..code then properly compiles and the spreadsheet works fine for them.I don't really understand why it fails on the Date() function, as that is VBA function, not an Outlook function.