Running Adodb mdx connection with Intergrated Security

[Herman Moller]

Hello,

Client has a legacy TM1 system. This system goes way back with over 8 years of history. At the time they didn’t have dynamic subsets so using VBA and ADO a system was written to give them the linkage with MDX they required.

The problem now comes in is that the client is now using Integrated Login. Would they still be able to use the current ADO and VBA Code to connect to TM1 or has it become obsolete?

Connection String in VBA

AdoCon.ConnectionString = "Provider=TM1OLAP.1;Data Source=" & tm1Server & ";User ID=" & sUserName & ";Password=" & sPassWord

TIA

[Eric]

What about using security setting:

Code: Select all

SecurityPackageName=Kerberos
IntegratedSecurityMode=2

that would allow integrated login and named login?

[ScottW]

Hi Herman,

I think the previous post is a little off the mark as you have said integrated login is already implemented. To answer your question, no change should be required to the VBA code for the OLEDB connection (other than you will need to substitute a value for user name and password if this is no longer being captured in the excel application.) The OLEDB provider for MDX support requires a separate connection to the server so is still required even if using integrated login.

Note that although no change in the code to establish the MDX connection is needed, if the TM1 server / client version is upgraded then it would be worthwhile testing the code as TM1's implementation of MDX has changed over time and this can sometimes result in breakage of code.