Accessing MAS 90 with ODBC in Visual Studio 2005

[ceegh]

Hello all,

I am trying to write a program in Visual Studio 2005 that gets info from MAS 90 version 4.1 using ODBC. Unfortunately, I can not retrieve any table information after adding the ODBC connection to my forms. Although I am able to retrieve simple queries still (like "SELECT * FROM SO_SalesHistory") I have problems with queries that involve parameters. The ODBC connection keeps timing out.

I know my ODBC is working right because I am able to use my trusty third-party ODBC query program to do all kinds of operations with the MAS 90 connection without issue. So it is only in Visual Studio that I have problems.

Any information would be very helpful.

Thank you.

 

[BigLouie]

The SOTAMAS90 ODBC driver is no great shakes. It does not handle queries involving parameters very well or all in some cases. I normally build another query based on first query and put the parameters in there.

 

[ceegh]

Thanks for the reply BigLouie.

What is confounding me is that I never had a problem with Visual Studio 2003, and when I do the same query outside of VS (Query Tool v. 4.1.1.5 by George Poulose, BTW) it performs without issue.

I just attempted to use 2008 with the same issues.

This lack of a list of tables bothers me too. I can't help but think that something VS 2005 and newer is doing breaks when using the MAS ODBC connection.

Or you able to see the list of tables for a MAS 90 connection when using Visual Studio 2005/2008?

 

[mlstephens]

Hello, I have been given a task to move data from Mas90/200 into a SQL database using VS 2005 and VB.Net. I can't seem to view the tables thru the ODBC driver supplied by Sage but in the Server Explorer I can run queries against the Inventory and ARCustomer tables. I am new to VB.Net so can some show or email me some code samples of how to set up the connection, dataadapter and dataset objects or is there a better way. I tried to use VI to move the data into temp tables in a SQL database and then sync the sql data up with our online system but VI is buggy. Any help is greatly appreciated.