This is a new security feature with Office XP. Starting with Microsoft Office XP, a user must grant access to the VBA object model before any Automation code written to manipulate VBA will work. This would make the project more manageable for re-distribution. You may want to consider moving the code into a resource file that you can compile into your application, and then extract into a temporary file when needed at run time.
The sample uses a static text file for the code module that is inserted into Excel.
The following sample demonstrates inserting a code module into Microsoft Excel, but you can use the same technique for Word and PowerPoint because both incorporate the same VBA engine. This article demonstrates how to dynamically add a VBA module to a running Office application from Visual Basic, and then call the macro to fill a worksheet in-process. This can boost overall execution speed for your application and help alleviate problems if the server only carries out an action when a call is made in-process.
When automating an Office product from Visual Basic, it may be useful to move part of the code into a Microsoft Visual Basic for Applications (VBA) module that can run inside the process space of the server.
0 kommentar(er)
