| Home |
| Search |
| Today's Posts |
|
#1
Posted to microsoft.public.excel.programming
|
|||
|
|||
Late Binding/Object Library Probelms
Hi, I was advised to use 'late binding' here -
http://groups.google.co.uk/group/mic...4381bb5c2a6bb1 - as I was updating and saving Excel files on my machine, for other users who have a previous version of Office.. I'm going through all my Subs using i.e "Dim i as Integer" but I'm having a problem with some of the code. I had to change "LEFT()" to "VBA.Strings.LEFT()", and now it has a problem with "xlShiftLeft". Does anyone know what I should change this to, or if there is any other way round my Library problem?? I've only 'Late Binded' 2 modules out of 20 so far, so I'm sure they'll be more problems.. Cheers Tony |
| Thread Tools | Search this Thread |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Forum | |||
| Late Binding issue with Excel.Application object | Excel Discussion (Misc queries) | |||
| Late binding to Excel from Access causing Object error | Excel Discussion (Misc queries) | |||
| VB Extensibility library and "late binding" | Excel Discussion (Misc queries) | |||
| Late binding to .XLA library?? | Excel Programming | |||
| VBA References - when is Office Object Library Reference set? Best practice re. Early/Late binding ... | Excel Programming | |||
Threaded Mode
