![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Load or Install Application by Code I am new to VBA and I am looking for a snippit of code that will allow me to automate (install) a Add In for Excel. Can someone direct me in the right direction so I get get started on this. Is their something already built and I can change some of the code to fit mine. Any help is appreciated. Thank you |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Load or Install Application by Code TKM wrote: Quote: > I am new to VBA and I am looking for a snippit of code that will allow me to > automate (install) a Add In for Excel. I haven't done this, but the XL help file has an explanation of how to do it. I suggest you turn on the XL Macro Recorder, go through the steps to install the addin (manually), and then turn off the recorder. The recorder will provide you with VBA code that reflects what you did (to install your addin). Converting the VBA code to vbScript is relatively easy. I have included "my usual discussion" on this (a.k.a., boilerplate) below. cheers, jw ____________________________________________________________ You got questions? WE GOT ANSWERS!!! ..(but, no guarantee the answers will be applicable to the questions) --- <boilerplate: using macro recorder to script msWD/XL> --- I don't have any scripts handy, but my standard advice for a situation like this is to turn on your excel macro recorder, go through the operation you want to do "manually" (say, for the first two worksheets), then turn off the macro recorder. Go to the editor for macros, and pick out the vba macro code. You then convert the vba to vbs -- not too hard to do -- but there are a couple of things to watch out for. The most common "thing to watch out for" is named arguments to functions or subs. You are going to have to enter the argument values (without the names) in their proper order. A more definitive statement of "things to watch out for" (when converting vba to vbs) may be found in the ng archives. Go to: http://groups.google.com/advanced_group_search Also, there are many postings about using excel's automation interface, and converting vba to vbs in this very newsgroup, which can also be located using google's group search. --- <end of macro recorder boilerplate> --- |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Using only 1/3 page file, but unable to load application | Vista General | |||
| unable to load webpages after an application is run | Vista General | |||
| Code 8004888d can't sign in Msnger or install beta 8.5 code 0x8009 | Vista security | |||
| DVD not load CODE 39 | Vista hardware & devices | |||
| dvd no load CODE 39 | Vista General | |||