Just wondering if anyone has found a solution to this. I'm running into the same issue.

Unfortunately I was not able to find a solution in time and was forced to use a SQL Server instance to mirror the Sage data, then pulled from that. You can also used a linked server and query using that as well.

jreynolds, if your message is addressed to me then no, I did not find a solution other than the one I referred to in my last post. I honestly don't think that there is a way to get this to work unless an update comes out for the odbc driver that addresses this issue.

It was for either of you. Do you have any information on setting up a linked server to the Mas database?

The solution I found may be something that was unique to my scenario. I have my website running on an isolated machine (the webserver), with it's own domain seperate from our internal domain. We punch through our firewall to gain access to the internal domain where the MAS installation is located. I could gain access to the MAS database from the webserver by using the ip address of the internal server where mas is located with a DSN. However, whenever I tried to access the BOI or the database from the actual website, using the standard application pool identity it didn't work. I googled around and found that if I used the same user name AND password, in the application pool identity, it would work. Sure enough, I tried it and it did. For example, my application pool identity could be WebServer/Joe with a password of 123456 and as long as my internal domain network was the same (InternalDomain/Joe with a password of 123456) it would work. Craziest thing I have seen in a while, but it's all up and running. Not sure if this will help in your scenario. Also, I found that queries to MAS not through the BOI, but standard database queries were extremely slow and killing the speed on my site. I ended up doing a nightly copy of the MAS tables I reference in the site over to SQL server on the webserver machine. It was much faster for me.

Thanks! This is what we did and it fixed the problem. We switched the app pool to run under a named account.