<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 28, 2016, at 7:38 PM, Julian Hyde <<a href="mailto:julianhyde@gmail.com" class="">julianhyde@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">[…] I suspect that Microsoft have quietly changed the order since the first MDX specification. That would explain why Oracle/Essbase[1] and IBM[2] have made the same mistake that Mondrian and olap4j have.</span></div></blockquote><br class=""></div><div>FWIW, mondrian-olap [1] was also bit by that bug: <a href="https://github.com/rsim/mondrian-olap/pull/35" class="">https://github.com/rsim/mondrian-olap/pull/35</a></div><div><br class=""></div><div>[1] <a href="https://github.com/rsim/mondrian-olap" class="">https://github.com/rsim/mondrian-olap</a></div><div><br class=""></div><div>—<br class="">Manuel Aristarán <<a href="mailto:manuel@jazzido.com" class="">manuel@jazzido.com</a>><br class=""><a href="http://jazzido.com" class="">http://jazzido.com</a></div><br class=""></body></html>