Hi Folks,
We have a VBA Excel macro that's been in use in our enterprise for at least 5-10 years. The macro makes use of the SASWorkspaceManager 1.1 Type Library to connect to our Workspace Server to extract SAS data into Excel. We have some beta testers of MS Office 365 who are getting errors during the SAS connection step from the same VBA macro. The chief difference is that o365 is running as a 64bit app on Win11(x64) in the beta test environment while previously it runs in 32bit MS Office Excel installed on Win10(x64).
The error message is not very helpful. Something like, "Object not registered." It is raised in the VBA code with the first reference to SASWorkspaceManager during an object declaration. I'm wondering if this a bitwise issue between o365 and the SAS library.
The users are able to connect to the SAS Metadata Server without issue from the SAS Add-in in o365 Excel.
