Tom,   I thought I'd send you a checklist of some things that I've tried before that have helped get the add-in loaded.  Some you may have already tried, some may be things that you can try.  Hopefully one of them gets it working for you.   A. Checking for disabled items in Excel      1. Open Excel, go to File->Options      2. On the Add-in page, there are 3 sections: Active, Inactie, and Disabled.  Check which list the SAS Add-in appears in.      3. If it appears in the Disabled list, go to the "Manage" combo box at the bottom and choose Disabled Items, then click Go...  Click on the SAS Add-In in the list of items to re-enable, and then Close.      4. Next, click on COM add-ins in that same combo box, and click Go...  Check the checkbox next to the SAS Add-in and click OK.  This should cause the add-in to load.      5. If it does NOT load, go back to File->Options->add-ins->COM addins->Go...  In this dialog if you select the SAS Add-in, there will be a load behavior at the bottom.  If there was an error during loading, it will put it here.  This will let us know if Excel is at least trying.   B. Checking the registry directly      1. Run regedit (as the user who invokes office)      2. Navigate to the following key:  HKEY_CURRENT_USER\Software\Microsoft\Office\Excel\Addins\SAS.ExcelAddin      3. See what the LoadBehavior is set to.  You want it set to 3.   C. Reset your add-in registry settings with SwitcherUtility      1. From a command prompt, navigate to the directory where you have the Add-In installed.      2. Run:   SwitcherUtility.exe ?      3. This shows a list of all the command line arguments.  This has some extra options that are not available in the UI.      4. Run:   SwitcherUtility reset            // This will reset information in the current user portion of the registry.  You want to do this as the user who is running Office, so that user's registry settings are reset, not the administrators.      5. See if this resolves the issue      6. Run:  SwitcherUtility resetall         // This will reset information in the local machine portion of the registry as well.  You must be running as an administrator to do this.      7.  See if this resolves the issue      8.  Run:  SwitcherUtility register     // This will re-register the add-in assemblies   D. Are you in a virtualized environment?  I've seen cases where each time a user logs in, their add-in gets disabled.  This was because their registry was getting "reset" each time they logged in, and the values that were being reset had the add-in disabled.  It doesn't sound like this is your case, but if it is, it's something to talk about with your system administrator.   E. Run the VSTO file      1. Go to the folder where you installed the SAS Add-in.      2. Find SAS.ExcelAddin.vsto      3. Double-click this file      4. This is essentially using the vsto file to register the add-in instead of our own process.  I don't usually suggest this, but when nothing else seems to be working to get the add-in enabled, this will often give a more helpful reason for the failure.     Hopefully one of these strategies will do the trick.  Feel free to contact me if you continue to have issues getting the add-in to load and I can take a closer look.   Tim Beese   ... View more

I took a look at the VBA that you're using and at first glance everything looks correct.  I attempted to replicate your issue and created my own stored process that used two input streams, and I was able to get it to work correctly.  The only thing that I changed from your example was the path of the stored process (pointed to my own), and the names of the input streams.   I used Enterprise Guide to create my stored process and in doing so, I was restricted to 8 characters for the name of my input stream in the stored process wizard.  Your 2nd input stream is defined as "VARIAVEIS", which is 9 characters.  Perhaps there is a limit on the length of the stream name?   I would suggest using stream names that are 8 or less characters to see if that makes a difference.  I used stream1 and stream2.  If there is some sort of limit being enforced, perhaps going through the UI handles that for you, but when automating, it does not.  Maybe the longer stream name is causing some sort of problem on the server that makes both streams invalid?   Other than the stream length, it looks correct to me.  The streams variable is a SAS Add-In scripting variable that stores the name/range internally, so from the VBA debugger it may look empty but not necessarily be empty.  When I looked at that field in my VBA debugger it didn't show anything, but my stored process executed cleanly.   Hope this helps, Tim Beese ... View more

Since you're using VBA to refresh results that were created by the Add-In for Microsoft Office, it is the SAS Add-In that is putting your row numbers back in.  The reason that the row numbers are there is that when you originally opened the data, you must have had the checkbox for "Insert record numbers in the first column" selected.  Once you do that, the Add-In will put the record numbers there, and will put them back each time that you refresh.   To make this stop, place your selection within the table that you want to change, and go to the SAS tab on the ribbon.  Select Properties.  This will bring up the properties for this content.  On the Data tab of the Properties dialog there will be a checkbox for "Show record numbers".  Uncheck that and click OK.  Now when you refresh the table, the record numbers should not be rendered.   You can change your global option, SAS->Tools->Options ->Data->Show Record Numbers, so that future datasets you open will not have the row numbers.  But, this does not affect tables that have already been rendered in the document.  Once there, the only way to change their behavior is through the properties dialog.   Hope this helps, Tim Beese ... View more