Dr.K
04-10-2009, 09:09 AM
I'm building a tool that processes about 800 PowerPoint presentations at a time. It pulls down data through ADO to populate certain slides with data. Since this is a big batch, speed/eficiency is important!
The underlying PowerPoint Presentation template was given to me to automate, so I didn't make it myself. Some of the custom slides contain PowerPoint Tables, and some contain embedded Excel Worksheet Objects. If I want to, I can make them go through and make all the data slides consitently one kind or the other.
Which is faster, Table or Embeded Workbook?
Also
Does Early-Binding to Excel make a speed difference?
Right now, I've got an Excel object that I Late-Bind like this:
If ppShape.Type = msoEmbeddedOLEObject Then
Set objWB = ppShape.OLEFormat.Object
The code that does the actuall work is a separate Sub that runs in a loop. Does this mean that it will load the Excel OLE code EVERY time the Sub runs? If so, can/should I build a routine into the main Sub that Gets/Creates an Excel Object, to ensure that the code is loaded once and only once?
The underlying PowerPoint Presentation template was given to me to automate, so I didn't make it myself. Some of the custom slides contain PowerPoint Tables, and some contain embedded Excel Worksheet Objects. If I want to, I can make them go through and make all the data slides consitently one kind or the other.
Which is faster, Table or Embeded Workbook?
Also
Does Early-Binding to Excel make a speed difference?
Right now, I've got an Excel object that I Late-Bind like this:
If ppShape.Type = msoEmbeddedOLEObject Then
Set objWB = ppShape.OLEFormat.Object
The code that does the actuall work is a separate Sub that runs in a loop. Does this mean that it will load the Excel OLE code EVERY time the Sub runs? If so, can/should I build a routine into the main Sub that Gets/Creates an Excel Object, to ensure that the code is loaded once and only once?