Home |
Search |
Today's Posts |
#4
![]() |
|||
|
|||
![]()
I haven't tested this, but the first thing I'd do is add the application object "Excel." before each excel object declaration.
i.e. Dim destWB As Excel.Workbook and not Dim destWB As Workbook Also - I'd avoid using Excel constants such as xlPasteValues. I'd suggest looking up the constant value then declaring it as a number. If this doesn't work as is, you may also need to fiddle with <Application.|<Creator.|<Parent.|... accessor objects (in varying combinations) to specify to the VBA engine that it's the Excel object embedded within the current Application that you're referring to. Sorry I can't be more specific than that - I haven't got time to research it fully at the moment. Suffice to say that I've used the Creator and Parent properties a number of times in varying configurations when working between mixed-application documents. The correct sequence to use is not always obvious. Regards, BizMark Quote:
|
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Sending from excel to word template | Excel Discussion (Misc queries) | |||
Excel crashes while opening excel file imbeddied with macros | Excel Discussion (Misc queries) | |||
Print Excel charts in Word 2003 with fixed size | Charts and Charting in Excel | |||
TRYING TO SET UP EXCEL SPREADSHEET ON MY COMPUTER | New Users to Excel | |||
Excel startup switches | Excel Discussion (Misc queries) |