named server not found

[telula]

Hello,
I have a spreadsheet that users use to connect to TM1.

sConnect = "DATA SOURCE=tm1prod;PROVIDER=TM1OLAP;Location=" & loc
where loc = Application.Run("OPTGET", ("AdminHost"))
This works in our production environment but when we change it to
sConnect = "DATA SOURCE=tm1dev;PROVIDER=TM1OLAP;Location=" & loc in our dev environment, I got an error message 'tm1dev':The named server was not found.

Can anyone help?

[Steve Rowe]

Hi telula,

Not really sure what you are doing with the what you have written, you'll need to provide some more detail if you.

The most obvious things are that the client cannot see the dev server or the dev server is registered on a different admin host or it was run up with the same port number in the cfg and can't be connected to.

Cheers,

[Steve Vincent]

It must be that the adminhost entries do not have that server running on them, all it can connect to is what the user can see in the list of services in server explorer. It might be valid but if the client doesn't see it there then it won't play.

As an aside (and why i'm replying to this nearly 6 months late!) the code you have for OPTGET bares no resemblance to that in the help files, but surprisingly yours works and the help doesn't!! Thanks, saved me some head scratching

[Alan Kirk]

As an aside (and why i'm replying to this nearly 6 months late!) the code you have for OPTGET bares no resemblance to that in the help files, but surprisingly yours works and the help doesn't!! Thanks, saved me some head scratching

Actually you had me scratching my head there for a minute, then I realised what you meant.

The 9.0 Help file example's syntax shows how the function is used in an old Macro 4.0 sheet. (Which is, I grant you, kinda like shoeing a horse. 100 years ago lots of people knew how to do that, but not so many now. Similarly 15 years ago lots of people knew how to write Excel 4.0 macros or their Lotus 1-2-3 counterparts, but it's now an almost lost art.) This macro 4.0 syntax is similar to the way the function would look if it were a worksheet function... which it ain't, but it still is the Macro 4.0 syntax. However if used in VBA the function needs to be called via the Application.Run method. (I'm so used to this that I just do the conversion in my head these days which is why I didn't pick up on what you were saying.) The brackets around the argument shown in the original post are unnecessary, but harmless.

The Help file does explain it; see the topic "Accessing macro functions" and the links that run from there.

[Alan Kirk]

The 9.0 Help file example's syntax shows how the function is used in an old Macro 4.0 sheet.
{Snip}
The Help file does explain it; see the topic "Accessing macro functions" and the links that run from there.

Afterthought: It's necessary to retain some reference to version 4.0 macro functionality since that's what most of those functions were written for back in the day, and it's the reason that they're called "macro" functions in the first place. However you won't get any argument from me that those atavistic throwbacks to Perspectives 2.6 and Excel 5 should probably have long since been de-emphasised in favour of the VBA usage, given that VBA has been the dominant automation tool in Excel for, oh, what, say 14 years now, or perhaps a little less allowing for the transition time after Excel for Windows 95 came out?

Perhaps IBM'll look to that when they get through splitting up the help files so that you can't search all of them at once.