"Farouk Jivraj" <fjivraj@mountrowcapital.com> wrote in message <h38g0k$aob$1@fred.mathworks.com>...
> Hi all, I was having this same problem but managed to find the solution! Hopefully it works for everyone else.
>
> FYI: I'm using Vista Home Premium (x64) as the client to connect to a SQL Server 2008 instance which is on the same machine.
>
> As we all figured, it's all to do with the ODBC configuration. I guess we all did the same thing, we added a new User Data Source (User DSN) item for the database in question. Trying to connect Matlab after this no doubt failed for all of us. What needs also to be done is to add a new System Date Source (System DSN) item for the respective database that we want access to.
>
> After doing this, restart Matlab and try to connect to the database in connection through the usual "database" command...this should fix the problem...it did for me.
>
> Good luck.
> fj
I tried the System DSN but it did not work for me. I called Matlab support and asked them about this issue. This is a known problem with no workarounds. They had no other suggestions other than using the JDBC driver.
Jeff
> Hi all, I was having this same problem but managed to find the solution! Hopefully it works for everyone else.
>
> FYI: I'm using Vista Home Premium (x64) as the client to connect to a SQL Server 2008 instance which is on the same machine.
>
> As we all figured, it's all to do with the ODBC configuration. I guess we all did the same thing, we added a new User Data Source (User DSN) item for the database in question. Trying to connect Matlab after this no doubt failed for all of us. What needs also to be done is to add a new System Date Source (System DSN) item for the respective database that we want access to.
>
> After doing this, restart Matlab and try to connect to the database in connection through the usual "database" command...this should fix the problem...it did for me.
>
> Good luck.
> fj
I tried the System DSN but it did not work for me. I called Matlab support and asked them about this issue. This is a known problem with no workarounds. They had no other suggestions other than using the JDBC driver.
Jeff