Office 365 causes errors in VBA code for SAS object

I got Microsoft Visual Basic Run-time error '-2147221164(80040154)': class not registered

when I got Office 365 installed and ran the following vba code with SAS object:

Public Sub test ()

  Dim obWM As SASWorkspaceManager.WorkspaceManager
  Set obWM = New SASWorkspaceManager.WorkspaceManager

End Sub

Please help if you've seen something like this, thank you!

I have no idea what that is but does it require a reference to be checked in the vba editor, maybe?

Do you have the SAS API library installed for Excel VBA? Was the same code running correctly in a prior version of Excel? If you upgraded Excel, did you switch from 32-bit to 64-bit when you upgraded?

Administrative Note:

Welcome to the forum.

We would very much like to help you with your query, however we recommend that you include code tags around your code.

Please take a moment to add the tags. Posting code between [code] [/code] tags makes your code much easier to read and copy for testing, and it also maintains VBA formatting.

Please see Forum Guideline #2 about code tags and adjust accordingly. Click on Edit to open your post, then highlight your code and click the # icon at the top of your post window. More information about these and other tags can be found here.

Jeff,

Yes, I have the SAS API library installed and the same code was running correctly in a prior version of Excel (32-bit). Once I switched to Office 365 (64-bit), the "class not registered" error showed up for that piece of code.

thank you!

You probably don't have a 64bit compatible version of the library then, in which case it won't work with 64bit Office.

See if you can locate where the dll is and that may give you an indication (eg if it's in Program Files (x86) it's a 32 bit program, so the dll is probably 32bit too.), or it might specify it in the properties of the file.

The add-in contains the API/dll. IT said the add-in for 365 is 64-bit, and your current add-in is in the x86 folder which implies it's 32-bit. Ask IT for the latest add-in. You can remove the old one, add the new one, check that as a reference, and hopefully be good to go.

I found this help page at sas help center: https://documentation.sas.com/doc/en...tlxhlbjzcd.htm

so for 64-bit windows, the default has two directories and I found both in my computer.

I found this on google:

The easiest method to find out if a DLL, UFL, or EXE is 32 or 64-bit is to open it in Notepad or another text editor such as Notapad++. After opening the file in a text editor, use the Find option to look for the 1st occurrence of the word PE. The letters after the PE header denote if the file is 32-bit or 64-bit.
· PE L = 32-bit (x86)
· PE d† = 64-bit (x64)

And I opened the dll file with a notepad and find PE L, so it is 32-bit. Did anyone used this method to test a dll file to be 32/64 bit? Is it true?

That "easiest method" sounds like nonsense to me. Those files are binary, not ASCII, and Notepad can't read them. There might be an ASCII string embedded in a header or something but I think you would need a hex editor to read it.

Notepad can open binary files just fine - they just look like gibberish for the most part.

I picked a .exe at random and opened it in a text editor. If your text editor has the ability to open this type of file you can see the content. Here are the first characters.

MZP······ÿÿ··¸·······@···································
··º·´ Í!¸
LÍ!This program must be run under Win32

I also found this string near the beginning of the file:

PE··L

Not exactly the flag you mentioned but it could be similar.